Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c419abce5191990afd16a72c857d09ea736a303bf290003dbb25881329514270

Tx prefix hash: bf85a25e9d6cf9f7fa30d753a2be20772c7d5ea6807b6a30c92eb2b1a7e55c67
Tx public key: 13c4cfafa555785f17bd5601f72310ce2322695f8ae4f0c30146e0cc806949b1
Timestamp: 1648670048 Timestamp [UCT]: 2022-03-30 19:54:08 Age [y:d:h:m:s]: 02:241:18:52:14
Block: 469786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 692401 RingCT/type: yes/0
Extra: 0113c4cfafa555785f17bd5601f72310ce2322695f8ae4f0c30146e0cc806949b102110000000937cb3088000000000000000000

1 output(s) for total of 17.037435093000 dcy

stealth address amount amount idx
00: 67d949184fd623c3507be4d18eecb67abaf25f77b5a9f8fd9a83aa484843b7ef 17.037435093000 888800 of 0

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": 469796, "vin": [ { "gen": { "height": 469786 } } ], "vout": [ { "amount": 17037435093, "target": { "key": "67d949184fd623c3507be4d18eecb67abaf25f77b5a9f8fd9a83aa484843b7ef" } } ], "extra": [ 1, 19, 196, 207, 175, 165, 85, 120, 95, 23, 189, 86, 1, 247, 35, 16, 206, 35, 34, 105, 95, 138, 228, 240, 195, 1, 70, 224, 204, 128, 105, 73, 177, 2, 17, 0, 0, 0, 9, 55, 203, 48, 136, 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