Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6bf76054af5f5a5e29082952084aa57975f83b9ffdb8cd172ddf4224db53c64

Tx prefix hash: 5fb4672036bff5eb8e34210159f59607f1d44f9d29acb8a6b06b4f578be61f15
Tx public key: fdd78d7b533cc70b57f61c62296ac1d1d64df61e9c99c84263f750f8ab0f17fa
Timestamp: 1750473371 Timestamp [UCT]: 2025-06-21 02:36:11 Age [y:d:h:m:s]: 00:146:03:34:01
Block: 1309453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102303 RingCT/type: yes/0
Extra: 01fdd78d7b533cc70b57f61c62296ac1d1d64df61e9c99c84263f750f8ab0f17fa02110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae7fc3ea4f1d3ef2651e7bfa22d599d97ccbf6876fcf0144328dec5ad1d876cd 0.600000000000 1797070 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": 1309463, "vin": [ { "gen": { "height": 1309453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae7fc3ea4f1d3ef2651e7bfa22d599d97ccbf6876fcf0144328dec5ad1d876cd" } } ], "extra": [ 1, 253, 215, 141, 123, 83, 60, 199, 11, 87, 246, 28, 98, 41, 106, 193, 209, 214, 77, 246, 30, 156, 153, 200, 66, 99, 247, 80, 248, 171, 15, 23, 250, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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