Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bef1c3eef962dd0fa33d34bbdcd39e9249ab780ab134dd4f89cdc6bfbd389601

Tx prefix hash: d403d49582f9e3ecd0348fa2c42841a53f8bd14f987c3c137eeab52ba9443ef0
Tx public key: 40c1e5ab68e202fb977c049a35c60a3ddef7f341ff6b3325bf62b6ee81aed8ed
Timestamp: 1576994842 Timestamp [UCT]: 2019-12-22 06:07:22 Age [y:d:h:m:s]: 05:144:12:40:09
Block: 29480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1252737 RingCT/type: yes/0
Extra: 0140c1e5ab68e202fb977c049a35c60a3ddef7f341ff6b3325bf62b6ee81aed8ed0211000000074ac5aa02000000000000000000

1 output(s) for total of 490.163678181000 dcy

stealth address amount amount idx
00: ad330a6ad34c3b4071bbc0f380aca8844d460d852bcde3e13c3e0332f505303f 490.163678181000 48522 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": 29490, "vin": [ { "gen": { "height": 29480 } } ], "vout": [ { "amount": 490163678181, "target": { "key": "ad330a6ad34c3b4071bbc0f380aca8844d460d852bcde3e13c3e0332f505303f" } } ], "extra": [ 1, 64, 193, 229, 171, 104, 226, 2, 251, 151, 124, 4, 154, 53, 198, 10, 61, 222, 247, 243, 65, 255, 107, 51, 37, 191, 98, 182, 238, 129, 174, 216, 237, 2, 17, 0, 0, 0, 7, 74, 197, 170, 2, 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