Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 830ec7c338886f9ca16c01c6202275dbe5df3909d6b0005448182e696ef6d220

Tx prefix hash: bb6e83e96afbd2fa2a116421339d8073d70f48b8e190cd04e6a2e8ad3954d5d6
Tx public key: ea8189115d5db4b373c72b4b809e346bd5b57e1d78415e67b80eddb6e9ea2d1d
Timestamp: 1577161527 Timestamp [UCT]: 2019-12-24 04:25:27 Age [y:d:h:m:s]: 05:116:04:47:13
Block: 30349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1232977 RingCT/type: yes/0
Extra: 01ea8189115d5db4b373c72b4b809e346bd5b57e1d78415e67b80eddb6e9ea2d1d021100000003d81c26c0000000000000000000

1 output(s) for total of 486.902524518000 dcy

stealth address amount amount idx
00: e24230fc829efe057f0130815a58ed391a0ffb0667b810edf5ce7f248e69bea4 486.902524518000 50111 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 30359, "vin": [ { "gen": { "height": 30349 } } ], "vout": [ { "amount": 486902524518, "target": { "key": "e24230fc829efe057f0130815a58ed391a0ffb0667b810edf5ce7f248e69bea4" } } ], "extra": [ 1, 234, 129, 137, 17, 93, 93, 180, 179, 115, 199, 43, 75, 128, 158, 52, 107, 213, 181, 126, 29, 120, 65, 94, 103, 184, 14, 221, 182, 233, 234, 45, 29, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8