Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cbfcdbfba7c10fa81af38af3c717a8d8f988d02ea2c5f14c40cea01c2ea30d8

Tx prefix hash: 5080b767b0763e1847105181e938d5fecec947c34ff3931d5cdff70841f1a28d
Tx public key: d43b2b7b562f494c665a23d8a70dc21104f7724a37a1a733d9f54081c9db1038
Timestamp: 1763359172 Timestamp [UCT]: 2025-11-17 05:59:32 Age [y:d:h:m:s]: 00:065:04:32:55
Block: 1413894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46536 RingCT/type: yes/0
Extra: 01d43b2b7b562f494c665a23d8a70dc21104f7724a37a1a733d9f54081c9db1038021100000004da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1e0fd78499b760508fa918ef11e971f5725e0e444bebdf45fe25297ecec3794 0.600000000000 1902375 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": 1413904, "vin": [ { "gen": { "height": 1413894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1e0fd78499b760508fa918ef11e971f5725e0e444bebdf45fe25297ecec3794" } } ], "extra": [ 1, 212, 59, 43, 123, 86, 47, 73, 76, 102, 90, 35, 216, 167, 13, 194, 17, 4, 247, 114, 74, 55, 161, 167, 51, 217, 245, 64, 129, 201, 219, 16, 56, 2, 17, 0, 0, 0, 4, 218, 85, 72, 72, 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