Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f850742b97dd52ecaf69f14ea513df39db6f783aaaed6f1861e01306ec6c114

Tx prefix hash: e9530716d1af5ecc7a0b564bd3d67c7ee82680e541e988e17227653cb9cf404d
Tx public key: 2419bf7c7df75971d9f249dc3c96924a7fd7ed13f41d2994d680124ea0de03f0
Timestamp: 1719083863 Timestamp [UCT]: 2024-06-22 19:17:43 Age [y:d:h:m:s]: 00:291:09:03:56
Block: 1049951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208225 RingCT/type: yes/0
Extra: 012419bf7c7df75971d9f249dc3c96924a7fd7ed13f41d2994d680124ea0de03f002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5fe5fc6b6e98b5593222937b10bb22bb51e7636621e7050b094a8a4baef756d 0.600000000000 1520072 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": 1049961, "vin": [ { "gen": { "height": 1049951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5fe5fc6b6e98b5593222937b10bb22bb51e7636621e7050b094a8a4baef756d" } } ], "extra": [ 1, 36, 25, 191, 124, 125, 247, 89, 113, 217, 242, 73, 220, 60, 150, 146, 74, 127, 215, 237, 19, 244, 29, 41, 148, 214, 128, 18, 78, 160, 222, 3, 240, 2, 17, 0, 0, 0, 1, 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