Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 627efaf9cfd463bcaf5c437cc7a25a00fea07c67ef097fd0f3b07b6893f0388f

Tx prefix hash: cf42a3e70542565a6a1373e47d93ca411d6780cfd4048feced49dcd8eb6d3eeb
Tx public key: 3a95bc47e60ee5955624b7f4b373e11b5020b95fd6c6198ed16ccd73cf372b4a
Timestamp: 1753657498 Timestamp [UCT]: 2025-07-27 23:04:58 Age [y:d:h:m:s]: 00:159:14:50:58
Block: 1334816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112976 RingCT/type: yes/0
Extra: 013a95bc47e60ee5955624b7f4b373e11b5020b95fd6c6198ed16ccd73cf372b4a02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f861f31156c3f50b69cc0687cfdbf7045925882d9bb5f80a04cdd9bcb7a695f 0.600000000000 1822617 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": 1334826, "vin": [ { "gen": { "height": 1334816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f861f31156c3f50b69cc0687cfdbf7045925882d9bb5f80a04cdd9bcb7a695f" } } ], "extra": [ 1, 58, 149, 188, 71, 230, 14, 229, 149, 86, 36, 183, 244, 179, 115, 225, 27, 80, 32, 185, 95, 214, 198, 25, 142, 209, 108, 205, 115, 207, 55, 43, 74, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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