Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a32d080bec4d03409d49ec55687d326247b7d5b3d23f213bb28a8beb2c42b7ab

Tx prefix hash: b5526a39d32beb037039f5fb23a1ecafc3c14cce862de686341d8350577d0580
Tx public key: 5ea0337e8da3b5fddfb32dbc3a32421a16d48d2b5127ac6458b2cc0812ba5280
Timestamp: 1728503156 Timestamp [UCT]: 2024-10-09 19:45:56 Age [y:d:h:m:s]: 00:169:16:53:38
Block: 1128054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121072 RingCT/type: yes/0
Extra: 015ea0337e8da3b5fddfb32dbc3a32421a16d48d2b5127ac6458b2cc0812ba528002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8daa3c5a8dd7f84956594b73342837f30a81aa7710d6f85e0553160ef62e8ec8 0.600000000000 1610869 of 15

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": 1128064, "vin": [ { "gen": { "height": 1128054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8daa3c5a8dd7f84956594b73342837f30a81aa7710d6f85e0553160ef62e8ec8" } } ], "extra": [ 1, 94, 160, 51, 126, 141, 163, 181, 253, 223, 179, 45, 188, 58, 50, 66, 26, 22, 212, 141, 43, 81, 39, 172, 100, 88, 178, 204, 8, 18, 186, 82, 128, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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