Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4befb0d733de237450ba96efed02947a0ca33e8ba79c698df3a8d33e242b2916

Tx prefix hash: 607ecec8f21bc64efabbc411d9fa1cb5d48e9eccc4b242e74c5ed83e5a4c4ee1
Tx public key: 2162f31f91dc37c70c63f3dc3ab314e94dd20bed0ae69af87da0c5de14547e35
Timestamp: 1630009200 Timestamp [UCT]: 2021-08-26 20:20:00 Age [y:d:h:m:s]: 03:163:04:26:50
Block: 321373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 890911 RingCT/type: yes/0
Extra: 012162f31f91dc37c70c63f3dc3ab314e94dd20bed0ae69af87da0c5de14547e35021100000021cd14b6bf000000000000000000

1 output(s) for total of 52.863790708000 dcy

stealth address amount amount idx
00: 1230b5448c42e4f82f7b53f2715d35c4e83fa7075658f9ddb916e8a4fb094d09 52.863790708000 667175 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": 321383, "vin": [ { "gen": { "height": 321373 } } ], "vout": [ { "amount": 52863790708, "target": { "key": "1230b5448c42e4f82f7b53f2715d35c4e83fa7075658f9ddb916e8a4fb094d09" } } ], "extra": [ 1, 33, 98, 243, 31, 145, 220, 55, 199, 12, 99, 243, 220, 58, 179, 20, 233, 77, 210, 11, 237, 10, 230, 154, 248, 125, 160, 197, 222, 20, 84, 126, 53, 2, 17, 0, 0, 0, 33, 205, 20, 182, 191, 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