Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40dd432c6a89e6ffbc8be63f857b93aabf808b301075786b53122ec648444377

Tx prefix hash: f0cfb8e17521524de0ca8b7d89a02f226141e0654f1a68b51d9762007b97587c
Tx public key: 6b710a2e01527cc445ea0381fed3e5d3d6bdadcfbf6298e65baed2576976395f
Timestamp: 1730973317 Timestamp [UCT]: 2024-11-07 09:55:17 Age [y:d:h:m:s]: 00:145:11:00:26
Block: 1148442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103775 RingCT/type: yes/0
Extra: 016b710a2e01527cc445ea0381fed3e5d3d6bdadcfbf6298e65baed2576976395f0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d8f4eb1c516f1f37b05acd038df85a313970800c99a1d7cb65a6077b3366d5c 0.600000000000 1633285 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": 1148452, "vin": [ { "gen": { "height": 1148442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d8f4eb1c516f1f37b05acd038df85a313970800c99a1d7cb65a6077b3366d5c" } } ], "extra": [ 1, 107, 113, 10, 46, 1, 82, 124, 196, 69, 234, 3, 129, 254, 211, 229, 211, 214, 189, 173, 207, 191, 98, 152, 230, 91, 174, 210, 87, 105, 118, 57, 95, 2, 17, 0, 0, 0, 5, 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