Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2405ac01b4a2c303ca6a47c1dcd8f3e3f12599d1cfe08fde3d0ae3e25ec6d26

Tx prefix hash: 8bdde02b5f1be19efd24b0ae91d854152a0f92a204a52d8a2149b706e776133f
Tx public key: 872b9e3a047dc308b2801f81e74b375eb1cd395e07a25bfd44da3d21651acc4a
Timestamp: 1734736178 Timestamp [UCT]: 2024-12-20 23:09:38 Age [y:d:h:m:s]: 00:015:07:24:38
Block: 1179640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10928 RingCT/type: yes/0
Extra: 01872b9e3a047dc308b2801f81e74b375eb1cd395e07a25bfd44da3d21651acc4a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5a5810a23ea80e1b2f37ff93ac579c4eeb32f9d06b2385672e6ff3c78ff5bb8 0.600000000000 1666039 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": 1179650, "vin": [ { "gen": { "height": 1179640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5a5810a23ea80e1b2f37ff93ac579c4eeb32f9d06b2385672e6ff3c78ff5bb8" } } ], "extra": [ 1, 135, 43, 158, 58, 4, 125, 195, 8, 178, 128, 31, 129, 231, 75, 55, 94, 177, 205, 57, 94, 7, 162, 91, 253, 68, 218, 61, 33, 101, 26, 204, 74, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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