Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a2c37868c5f4c88304c0451b8eba83d1d9e127403941a59d1a8e865d5824635

Tx prefix hash: 4ac63bf89484a0b86e7862fce6e300e5a1dbbcedf5957b14328b96f0d664bb28
Tx public key: 77ec42a7ea5d822aaefc37136cd0f8e2936501cc5cdef30b92c47f235e3be66d
Timestamp: 1713295412 Timestamp [UCT]: 2024-04-16 19:23:32 Age [y:d:h:m:s]: 00:212:15:30:51
Block: 1001956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152242 RingCT/type: yes/0
Extra: 0177ec42a7ea5d822aaefc37136cd0f8e2936501cc5cdef30b92c47f235e3be66d02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bd4aca457a663f0eda7fccf75c924006eb19afd7419ee8a92262774eef545f4 0.600000000000 1462470 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": 1001966, "vin": [ { "gen": { "height": 1001956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bd4aca457a663f0eda7fccf75c924006eb19afd7419ee8a92262774eef545f4" } } ], "extra": [ 1, 119, 236, 66, 167, 234, 93, 130, 42, 174, 252, 55, 19, 108, 208, 248, 226, 147, 101, 1, 204, 92, 222, 243, 11, 146, 196, 127, 35, 94, 59, 230, 109, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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