Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fee1fb3372cc56f3ca6598deaa036c1c4f627475315c834713a747323e11ff09

Tx prefix hash: b5183a7f0291ce0aed5fbdc103f378ccbfdadad6f890965cd0c5e51daa1ff3ff
Tx public key: 6dd2ef1ab1d373c0b31427c54ef5c3244f14167622141a1a8a129c964d0d48ed
Timestamp: 1728249980 Timestamp [UCT]: 2024-10-06 21:26:20 Age [y:d:h:m:s]: 00:179:04:41:37
Block: 1125945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127862 RingCT/type: yes/0
Extra: 016dd2ef1ab1d373c0b31427c54ef5c3244f14167622141a1a8a129c964d0d48ed02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2b599279903f1c7033d968bb08f762a880994b60477c5bf9aa7c985ed92a7aa 0.600000000000 1608718 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": 1125955, "vin": [ { "gen": { "height": 1125945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2b599279903f1c7033d968bb08f762a880994b60477c5bf9aa7c985ed92a7aa" } } ], "extra": [ 1, 109, 210, 239, 26, 177, 211, 115, 192, 179, 20, 39, 197, 78, 245, 195, 36, 79, 20, 22, 118, 34, 20, 26, 26, 138, 18, 156, 150, 77, 13, 72, 237, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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