Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4e0cf52cfa81ece77fa13f01c03e35645b6546c658c42c9b3983f640264771b

Tx prefix hash: 7cdccd6b357c71577b19c53b02ec01dbd84f8023b1154dc30379bcf72bf909e4
Tx public key: 902deec24b91453121fead4f3fe10a40b908e20dc7c3b0bea81a328a719b0143
Timestamp: 1730336502 Timestamp [UCT]: 2024-10-31 01:01:42 Age [y:d:h:m:s]: 00:083:22:18:10
Block: 1143160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60010 RingCT/type: yes/0
Extra: 01902deec24b91453121fead4f3fe10a40b908e20dc7c3b0bea81a328a719b01430211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efcb44498e48c1d7cf2911cec3d18b2f00e2a247dd2141a7aeca7ea5dc46e703 0.600000000000 1627023 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": 1143170, "vin": [ { "gen": { "height": 1143160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efcb44498e48c1d7cf2911cec3d18b2f00e2a247dd2141a7aeca7ea5dc46e703" } } ], "extra": [ 1, 144, 45, 238, 194, 75, 145, 69, 49, 33, 254, 173, 79, 63, 225, 10, 64, 185, 8, 226, 13, 199, 195, 176, 190, 168, 26, 50, 138, 113, 155, 1, 67, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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