Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68d439dfba4dcb4b12f7f548997f815f3c160a7d373c4f4545b44d146450cc0b

Tx prefix hash: 06676361888284ff3edb64074a9f988837426f2ff1eaf8f05a4dc9d722a1016d
Tx public key: 68fe2df76ee6c60a8fef7816f0ad2d78969faa07e9b4fb7160fe0e5c083b3242
Timestamp: 1715242086 Timestamp [UCT]: 2024-05-09 08:08:06 Age [y:d:h:m:s]: 00:331:13:34:19
Block: 1018112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236999 RingCT/type: yes/0
Extra: 0168fe2df76ee6c60a8fef7816f0ad2d78969faa07e9b4fb7160fe0e5c083b32420211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0060e2e819c15902ba2bce487471837faf5d2b7a8aa6989950f4b2104696852b 0.600000000000 1481897 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": 1018122, "vin": [ { "gen": { "height": 1018112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0060e2e819c15902ba2bce487471837faf5d2b7a8aa6989950f4b2104696852b" } } ], "extra": [ 1, 104, 254, 45, 247, 110, 230, 198, 10, 143, 239, 120, 22, 240, 173, 45, 120, 150, 159, 170, 7, 233, 180, 251, 113, 96, 254, 14, 92, 8, 59, 50, 66, 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