Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aa09287b5274327aa9ad37831a8d7248547ec0c2f335db70c94b4920987f97d

Tx prefix hash: e0400730bf4d4bca0172a4ce345f69951da5a17f75dfb7ec2880bb43d8a759ea
Tx public key: 3045b1f599d618163b6f500ae8e243f211eb1a6b9f4885a7c36bac38ccb42967
Timestamp: 1580620907 Timestamp [UCT]: 2020-02-02 05:21:47 Age [y:d:h:m:s]: 05:007:20:23:10
Block: 56887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157584 RingCT/type: yes/0
Extra: 013045b1f599d618163b6f500ae8e243f211eb1a6b9f4885a7c36bac38ccb42967021100000001b221b3d1000000000000000000

1 output(s) for total of 397.658781091000 dcy

stealth address amount amount idx
00: e3863c099cd9b4ffe1cada92c259987a94fa7fee1ccd2365f0732ff9e824eaff 397.658781091000 104904 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": 56897, "vin": [ { "gen": { "height": 56887 } } ], "vout": [ { "amount": 397658781091, "target": { "key": "e3863c099cd9b4ffe1cada92c259987a94fa7fee1ccd2365f0732ff9e824eaff" } } ], "extra": [ 1, 48, 69, 177, 245, 153, 214, 24, 22, 59, 111, 80, 10, 232, 226, 67, 242, 17, 235, 26, 107, 159, 72, 133, 167, 195, 107, 172, 56, 204, 180, 41, 103, 2, 17, 0, 0, 0, 1, 178, 33, 179, 209, 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