Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd3d172da258d1bf534f25dfdc429dcde03ade418f39671cbb6dca8cc8796f5d

Tx prefix hash: 135b8954389dfefec1eb2ac97109d56081727c4f5a90d8b05d00489a703c9188
Tx public key: ddf168b6f0a7762d3d53619e4937bc64cb70cc55f0be1d76bd504775cab37b26
Timestamp: 1696128012 Timestamp [UCT]: 2023-10-01 02:40:12 Age [y:d:h:m:s]: 01:190:03:16:39
Block: 859844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396930 RingCT/type: yes/0
Extra: 01ddf168b6f0a7762d3d53619e4937bc64cb70cc55f0be1d76bd504775cab37b26021100000006faf35c9c000000000000000000

1 output(s) for total of 0.868920277000 dcy

stealth address amount amount idx
00: 0cd1e6bd20e1e626abf457d8909361c648bac8aece65b4e36566be400fe75ed6 0.868920277000 1314092 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": 859854, "vin": [ { "gen": { "height": 859844 } } ], "vout": [ { "amount": 868920277, "target": { "key": "0cd1e6bd20e1e626abf457d8909361c648bac8aece65b4e36566be400fe75ed6" } } ], "extra": [ 1, 221, 241, 104, 182, 240, 167, 118, 45, 61, 83, 97, 158, 73, 55, 188, 100, 203, 112, 204, 85, 240, 190, 29, 118, 189, 80, 71, 117, 202, 179, 123, 38, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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