Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6af0dd39ee64e21d0f1c96e7c5f1cf96a067047f03a80617698172566bcabe73

Tx prefix hash: ee0be42d114abef96fb1d9bcb5ed1f2193a5f93588d06b758341930064b54bc3
Tx public key: b1e4f176aca610ba1cabd30e7da8b109f938fbb1f060c8c6bedf1d29e0571559
Timestamp: 1724895693 Timestamp [UCT]: 2024-08-29 01:41:33 Age [y:d:h:m:s]: 00:223:10:05:15
Block: 1098139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159546 RingCT/type: yes/0
Extra: 01b1e4f176aca610ba1cabd30e7da8b109f938fbb1f060c8c6bedf1d29e057155902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: adda6fb6e937855d3d03b385db907f0fd7a69a9bce10cc036cd3d4b6a7f21daa 0.600000000000 1573754 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": 1098149, "vin": [ { "gen": { "height": 1098139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "adda6fb6e937855d3d03b385db907f0fd7a69a9bce10cc036cd3d4b6a7f21daa" } } ], "extra": [ 1, 177, 228, 241, 118, 172, 166, 16, 186, 28, 171, 211, 14, 125, 168, 177, 9, 249, 56, 251, 177, 240, 96, 200, 198, 190, 223, 29, 41, 224, 87, 21, 89, 2, 17, 0, 0, 0, 3, 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