Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25a64b74fcb2099ff9b5a99903a5353c87daed75d06ff299c9a0da4b3c304f45

Tx prefix hash: 799d31e57e5b4bb7dbad8d938c212dce05bb1e75ecdc01f2d3712b13b2593467
Tx public key: c6f90be065194c2a14e4a2cf724fcbd31d21e0b69d06cde0b0af2b3f2466d60d
Timestamp: 1712717461 Timestamp [UCT]: 2024-04-10 02:51:01 Age [y:d:h:m:s]: 01:063:11:37:36
Block: 997158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306350 RingCT/type: yes/0
Extra: 01c6f90be065194c2a14e4a2cf724fcbd31d21e0b69d06cde0b0af2b3f2466d60d02110000000352d47e94000000000000000000

1 output(s) for total of 0.600070000000 dcy

stealth address amount amount idx
00: f08b6fef94848657f25f0c1dc5c92b3dbcb1c736b3c8c1d671eb63dca0d120fc 0.600070000000 1457586 of 0

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": 997168, "vin": [ { "gen": { "height": 997158 } } ], "vout": [ { "amount": 600070000, "target": { "key": "f08b6fef94848657f25f0c1dc5c92b3dbcb1c736b3c8c1d671eb63dca0d120fc" } } ], "extra": [ 1, 198, 249, 11, 224, 101, 25, 76, 42, 20, 228, 162, 207, 114, 79, 203, 211, 29, 33, 224, 182, 157, 6, 205, 224, 176, 175, 43, 63, 36, 102, 214, 13, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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