Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c2c3eca838dd4861f689faa76cd308f1f0aaa1ff6f0ffb18d1a70c082fad11e

Tx prefix hash: d3ba8523e6f302db128b7e725375830f52817c22aa23e4b174beb42bb2d50e35
Tx public key: 765eef1733a97df4f59d118954f2dd5ce39e65b2c020be34fdb37223f524e4b8
Timestamp: 1713529255 Timestamp [UCT]: 2024-04-19 12:20:55 Age [y:d:h:m:s]: 00:355:10:50:13
Block: 1003903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254112 RingCT/type: yes/0
Extra: 01765eef1733a97df4f59d118954f2dd5ce39e65b2c020be34fdb37223f524e4b80211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b96dcda59d9b42c0f6ff0c478644682d8be9240db10aee1a1f0eab4ddaa24f6c 0.600000000000 1464453 of 15

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": 1003913, "vin": [ { "gen": { "height": 1003903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b96dcda59d9b42c0f6ff0c478644682d8be9240db10aee1a1f0eab4ddaa24f6c" } } ], "extra": [ 1, 118, 94, 239, 23, 51, 169, 125, 244, 245, 157, 17, 137, 84, 242, 221, 92, 227, 158, 101, 178, 192, 32, 190, 52, 253, 179, 114, 35, 245, 36, 228, 184, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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