Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ad1d8370a938cc016494042a2bf84508a82407375d664ba450fb028cd3ba5df

Tx prefix hash: e76135842fec278af40c59e6ebdc2a0058f5a7de30be8409d9f55b24ec13f679
Tx public key: 04e9786ea6873925adf959a81fcd9fceab92b8066e5d0763e0bd691fd9c40c72
Timestamp: 1763085547 Timestamp [UCT]: 2025-11-14 01:59:07 Age [y:d:h:m:s]: 00:040:02:38:57
Block: 1411632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28707 RingCT/type: yes/0
Extra: 0104e9786ea6873925adf959a81fcd9fceab92b8066e5d0763e0bd691fd9c40c720211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd9b1937a25b2b62e1bcb891d81d9e395f9599e6e002405f405b2e9c3dd0966d 0.600000000000 1900095 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": 1411642, "vin": [ { "gen": { "height": 1411632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd9b1937a25b2b62e1bcb891d81d9e395f9599e6e002405f405b2e9c3dd0966d" } } ], "extra": [ 1, 4, 233, 120, 110, 166, 135, 57, 37, 173, 249, 89, 168, 31, 205, 159, 206, 171, 146, 184, 6, 110, 93, 7, 99, 224, 189, 105, 31, 217, 196, 12, 114, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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