Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bd99995a43934f66e626f2e1a801d022fefc6988fb65f21bc13aaa7e5928292

Tx prefix hash: 4ca1df64b8e003546141cdd7593804ec596ce3ce0f01763eae609aaf3ff1d4c2
Tx public key: c5a862698c45eebc1be5e8d5979ca2107dcf2fa04d67f0ed142766ed13e2cda1
Timestamp: 1756154156 Timestamp [UCT]: 2025-08-25 20:35:56 Age [y:d:h:m:s]: 00:133:03:20:07
Block: 1354364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95175 RingCT/type: yes/0
Extra: 01c5a862698c45eebc1be5e8d5979ca2107dcf2fa04d67f0ed142766ed13e2cda1021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e312a47f2b0d01289a0cb7fdf79f33732f937a6494d8a4c74a924c1394ed74fc 0.600000000000 1842351 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": 1354374, "vin": [ { "gen": { "height": 1354364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e312a47f2b0d01289a0cb7fdf79f33732f937a6494d8a4c74a924c1394ed74fc" } } ], "extra": [ 1, 197, 168, 98, 105, 140, 69, 238, 188, 27, 229, 232, 213, 151, 156, 162, 16, 125, 207, 47, 160, 77, 103, 240, 237, 20, 39, 102, 237, 19, 226, 205, 161, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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