Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52930104d740a0d500ca3bf0c7d67b94f67d583ce55971b60e41db4669eca153

Tx prefix hash: e60c6752b6260f6b96c48c10fd9c43858be16f663b0eb0d53f3e44319042c3dc
Tx public key: cf564862eaa769b4d47f76887a36ae4768374b542c0a549e7d7c55ba5325ee5d
Timestamp: 1758111906 Timestamp [UCT]: 2025-09-17 12:25:06 Age [y:d:h:m:s]: 00:071:20:03:11
Block: 1370412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51429 RingCT/type: yes/0
Extra: 01cf564862eaa769b4d47f76887a36ae4768374b542c0a549e7d7c55ba5325ee5d021100000005ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6e708d64eb66bc70fb2f75a7a99a3c18491d870bb8acaf13ed4e6ec2d6c3983 0.600000000000 1858487 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": 1370422, "vin": [ { "gen": { "height": 1370412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6e708d64eb66bc70fb2f75a7a99a3c18491d870bb8acaf13ed4e6ec2d6c3983" } } ], "extra": [ 1, 207, 86, 72, 98, 234, 167, 105, 180, 212, 127, 118, 136, 122, 54, 174, 71, 104, 55, 75, 84, 44, 10, 84, 158, 125, 124, 85, 186, 83, 37, 238, 93, 2, 17, 0, 0, 0, 5, 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