Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0374c1a646b31bddddc533c4e2bb728ea9ac872887f032729c0d1948c7d93e78

Tx prefix hash: 29680e70fdcb46deeffa619a16f7fb627c57656bc8752be26668531d9b3e46f1
Tx public key: 807dfc9555ff878ca80afadecc83cdbca0f48fb50c85c12a70e15396a1030e77
Timestamp: 1648616072 Timestamp [UCT]: 2022-03-30 04:54:32 Age [y:d:h:m:s]: 02:271:10:20:33
Block: 469357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 713595 RingCT/type: yes/0
Extra: 01807dfc9555ff878ca80afadecc83cdbca0f48fb50c85c12a70e15396a1030e7702110000000b06faf294000000000000000000

1 output(s) for total of 17.093290364000 dcy

stealth address amount amount idx
00: ae86ed79afdb79bb83003bf555a0d2c05251e1a32cb9b8b0bd64909ba8c0e083 17.093290364000 888289 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": 469367, "vin": [ { "gen": { "height": 469357 } } ], "vout": [ { "amount": 17093290364, "target": { "key": "ae86ed79afdb79bb83003bf555a0d2c05251e1a32cb9b8b0bd64909ba8c0e083" } } ], "extra": [ 1, 128, 125, 252, 149, 85, 255, 135, 140, 168, 10, 250, 222, 204, 131, 205, 188, 160, 244, 143, 181, 12, 133, 193, 42, 112, 225, 83, 150, 161, 3, 14, 119, 2, 17, 0, 0, 0, 11, 6, 250, 242, 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