Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae2aa83081e33a014565eb0b1cc64f216bb4d1bbdf36ae9a9d48c045c0c942f1

Tx prefix hash: 3a6808c826fcf60a355f5805b3ba2f01cccbadde504a23774129232afa68455f
Tx public key: 0332917c6ac5f0bb78fa678e8176ab4825fe1fc5284134ad428c291e8d497133
Timestamp: 1580617636 Timestamp [UCT]: 2020-02-02 04:27:16 Age [y:d:h:m:s]: 05:081:00:23:11
Block: 56860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1209904 RingCT/type: yes/0
Extra: 010332917c6ac5f0bb78fa678e8176ab4825fe1fc5284134ad428c291e8d4971330211000000138a2ee0d9000000000000000000

1 output(s) for total of 397.740705026000 dcy

stealth address amount amount idx
00: 28d8b7a5ff6debdde163a2e0e332f9eef8f1ec7e01755d62060eaf9dba6c5e24 397.740705026000 104857 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": 56870, "vin": [ { "gen": { "height": 56860 } } ], "vout": [ { "amount": 397740705026, "target": { "key": "28d8b7a5ff6debdde163a2e0e332f9eef8f1ec7e01755d62060eaf9dba6c5e24" } } ], "extra": [ 1, 3, 50, 145, 124, 106, 197, 240, 187, 120, 250, 103, 142, 129, 118, 171, 72, 37, 254, 31, 197, 40, 65, 52, 173, 66, 140, 41, 30, 141, 73, 113, 51, 2, 17, 0, 0, 0, 19, 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