Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca553c2c4ca2aaf70fe8a570aaa71d65b4b40ce5c2117d41d09fcc7ac48577f6

Tx prefix hash: 8cce7501e5063c8656786c6b208bd7b5b664dc5746fa1db1d2926a0f857c47f2
Tx public key: 26307ab128ad518f496288091741a161fad49fe4e7de293e1d6c0a9240c780a7
Timestamp: 1577813776 Timestamp [UCT]: 2019-12-31 17:36:16 Age [y:d:h:m:s]: 05:001:02:37:57
Block: 35917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150751 RingCT/type: yes/0
Extra: 0126307ab128ad518f496288091741a161fad49fe4e7de293e1d6c0a9240c780a702110000001d8a2ee0d9000000000000000000

1 output(s) for total of 466.651775719000 dcy

stealth address amount amount idx
00: da79df4e8703952c7d679446fe06af34b60e9914fb04a23c4b9f4d030486fb5e 466.651775719000 60659 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": 35927, "vin": [ { "gen": { "height": 35917 } } ], "vout": [ { "amount": 466651775719, "target": { "key": "da79df4e8703952c7d679446fe06af34b60e9914fb04a23c4b9f4d030486fb5e" } } ], "extra": [ 1, 38, 48, 122, 177, 40, 173, 81, 143, 73, 98, 136, 9, 23, 65, 161, 97, 250, 212, 159, 228, 231, 222, 41, 62, 29, 108, 10, 146, 64, 199, 128, 167, 2, 17, 0, 0, 0, 29, 138, 46, 224, 217, 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