Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6dd94c4db95e96a2d2eb2983f4787662172a8b630a7d291f7495f1eb76d13a3

Tx prefix hash: e8c0f78e69cc98dc5cfd0fc1ea3504e1ca297f0a5e48292f60832c6318c8d3b5
Tx public key: 4258e89e4f3e61fbe217d3025562139a14d0c4c4baf80cf363a4d2ff289b4a7e
Timestamp: 1762406999 Timestamp [UCT]: 2025-11-06 05:29:59 Age [y:d:h:m:s]: 00:047:23:07:13
Block: 1405995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34344 RingCT/type: yes/0
Extra: 014258e89e4f3e61fbe217d3025562139a14d0c4c4baf80cf363a4d2ff289b4a7e0211000000045dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f2c301821131168cb470fd20142d4e6021f8733d1134aa5bca70a0b1118add6 0.600000000000 1894376 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": 1406005, "vin": [ { "gen": { "height": 1405995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f2c301821131168cb470fd20142d4e6021f8733d1134aa5bca70a0b1118add6" } } ], "extra": [ 1, 66, 88, 232, 158, 79, 62, 97, 251, 226, 23, 211, 2, 85, 98, 19, 154, 20, 208, 196, 196, 186, 248, 12, 243, 99, 164, 210, 255, 40, 155, 74, 126, 2, 17, 0, 0, 0, 4, 93, 251, 190, 42, 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