Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8192a5c3157d047a8422bee3e96769e730bd206d4580839f4045be6725aa0cb7

Tx prefix hash: d30e9dfd9304a023feb832f3e593fe2dd4552461a2050ce1fb92a81553fcbaa2
Tx public key: 41b055e85fe8c55fc98d540cfbd4f0480578b69fe0adf67f5b79dd971f5890dc
Timestamp: 1632293622 Timestamp [UCT]: 2021-09-22 06:53:42 Age [y:d:h:m:s]: 03:100:15:50:25
Block: 338630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 848114 RingCT/type: yes/0
Extra: 0141b055e85fe8c55fc98d540cfbd4f0480578b69fe0adf67f5b79dd971f5890dc0211000000295d7cc334000000000000000000

1 output(s) for total of 46.342416079000 dcy

stealth address amount amount idx
00: 462c67bef64e1877726d884aec0ce58ce36274a66ba773cdbf8628b3eb31be81 46.342416079000 696841 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": 338640, "vin": [ { "gen": { "height": 338630 } } ], "vout": [ { "amount": 46342416079, "target": { "key": "462c67bef64e1877726d884aec0ce58ce36274a66ba773cdbf8628b3eb31be81" } } ], "extra": [ 1, 65, 176, 85, 232, 95, 232, 197, 95, 201, 141, 84, 12, 251, 212, 240, 72, 5, 120, 182, 159, 224, 173, 246, 127, 91, 121, 221, 151, 31, 88, 144, 220, 2, 17, 0, 0, 0, 41, 93, 124, 195, 52, 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