Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b5c5dda8d0b818f534ff9b5a935a8b108f8b5cf16c50a0c06b20a03a33f514e

Tx prefix hash: 014936a8554aba2148119399d2115004791967be91992b479bd4ef6fb542d8cc
Tx public key: 5124b9375c6cb7d0e0a86e452f8cc88df2195a70ba66d87ae30ed6811b2b0285
Timestamp: 1713380481 Timestamp [UCT]: 2024-04-17 19:01:21 Age [y:d:h:m:s]: 01:000:08:38:06
Block: 1002668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261202 RingCT/type: yes/0
Extra: 015124b9375c6cb7d0e0a86e452f8cc88df2195a70ba66d87ae30ed6811b2b02850211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 745d9bafd4693d1ed70f79ab0285581bf64f5b502509949eb1ef0f8c0003db4c 0.600000000000 1463186 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": 1002678, "vin": [ { "gen": { "height": 1002668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "745d9bafd4693d1ed70f79ab0285581bf64f5b502509949eb1ef0f8c0003db4c" } } ], "extra": [ 1, 81, 36, 185, 55, 92, 108, 183, 208, 224, 168, 110, 69, 47, 140, 200, 141, 242, 25, 90, 112, 186, 102, 216, 122, 227, 14, 214, 129, 27, 43, 2, 133, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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