Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 832ef01e923cb5b63fcd1898fb73129984abba0f064df5f53468a18d79ec582e

Tx prefix hash: add77d9715ef18a3ac943cbfd44e810180e862720650a6072a43c198c888a5c7
Tx public key: 80464f28db36dedc4a3ca48650fb5c793e4faa48b840a5dcbfd371ac7d897337
Timestamp: 1737109177 Timestamp [UCT]: 2025-01-17 10:19:37 Age [y:d:h:m:s]: 00:059:02:13:05
Block: 1199251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42019 RingCT/type: yes/0
Extra: 0180464f28db36dedc4a3ca48650fb5c793e4faa48b840a5dcbfd371ac7d897337021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acec8fdf45e1e48d4e3156c534243dd95c6f9e6e99fd861918a820eaed096bf4 0.600000000000 1685880 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": 1199261, "vin": [ { "gen": { "height": 1199251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acec8fdf45e1e48d4e3156c534243dd95c6f9e6e99fd861918a820eaed096bf4" } } ], "extra": [ 1, 128, 70, 79, 40, 219, 54, 222, 220, 74, 60, 164, 134, 80, 251, 92, 121, 62, 79, 170, 72, 184, 64, 165, 220, 191, 211, 113, 172, 125, 137, 115, 55, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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