Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0ee0fc2d852c8361e00ccaee254ad0580e7d957e1a7537cca43ac475f54f0ec

Tx prefix hash: 0dccd6330ea28e7e04322cc8c480a7655bfb86dfb48e9e60a0717cec792a4102
Tx public key: fc11e4e6e427760d38bb97968ccf6a743dd7b40173619eb3ad37b060dae3ed74
Timestamp: 1736046781 Timestamp [UCT]: 2025-01-05 03:13:01 Age [y:d:h:m:s]: 00:308:06:20:27
Block: 1190460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217814 RingCT/type: yes/0
Extra: 01fc11e4e6e427760d38bb97968ccf6a743dd7b40173619eb3ad37b060dae3ed7402110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f70cdf05e52bc83bfc6162badc401316050fb4ce7ca7ca49946b94d0cdb3ecdf 0.600000000000 1676977 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": 1190470, "vin": [ { "gen": { "height": 1190460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f70cdf05e52bc83bfc6162badc401316050fb4ce7ca7ca49946b94d0cdb3ecdf" } } ], "extra": [ 1, 252, 17, 228, 230, 228, 39, 118, 13, 56, 187, 151, 150, 140, 207, 106, 116, 61, 215, 180, 1, 115, 97, 158, 179, 173, 55, 176, 96, 218, 227, 237, 116, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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