Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d8a28245803f818f2579eb7c4df6e7662965510c5bea26fbca6f87735b219b2

Tx prefix hash: 8d987dcdd2efca3f4ca6d4fd3b04efbc71be5d541f233e294718178d59a842d4
Tx public key: 8e360d4b812e9d3219c9e13b666314d3b9742fc4dab814c0a2759435f311a708
Timestamp: 1578485061 Timestamp [UCT]: 2020-01-08 12:04:21 Age [y:d:h:m:s]: 04:326:22:56:43
Block: 41211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123011 RingCT/type: yes/0
Extra: 018e360d4b812e9d3219c9e13b666314d3b9742fc4dab814c0a2759435f311a7080211000000118a2ee0d9000000000000000000

1 output(s) for total of 448.179198249000 dcy

stealth address amount amount idx
00: a7e832b79cb4dcfa105e6a7ccddbadc33dc6ffde3ecfdd44c6049cfd3de75c0d 448.179198249000 73177 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": 41221, "vin": [ { "gen": { "height": 41211 } } ], "vout": [ { "amount": 448179198249, "target": { "key": "a7e832b79cb4dcfa105e6a7ccddbadc33dc6ffde3ecfdd44c6049cfd3de75c0d" } } ], "extra": [ 1, 142, 54, 13, 75, 129, 46, 157, 50, 25, 201, 225, 59, 102, 99, 20, 211, 185, 116, 47, 196, 218, 184, 20, 192, 162, 117, 148, 53, 243, 17, 167, 8, 2, 17, 0, 0, 0, 17, 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