Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb18906da490d8f426fb9b952b32050ab6a3e12b62d1f03ed4fc4c6ffc3fe22e

Tx prefix hash: 65980cfb6cfe9f4742393deca1c93ddcbd948efaa7f6e8b585b02ebefc1c1327
Tx public key: 1cd17f4ea047cd6509de35f639f2e69dc43d06d2d2ebc57ba23df43230424c3f
Timestamp: 1713517691 Timestamp [UCT]: 2024-04-19 09:08:11 Age [y:d:h:m:s]: 00:331:17:40:30
Block: 1003813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237160 RingCT/type: yes/0
Extra: 011cd17f4ea047cd6509de35f639f2e69dc43d06d2d2ebc57ba23df43230424c3f021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6f153b7f7312a68064ad33aaca8a794b7e4c20e5a92065968f4ee5580db2f6e 0.600000000000 1464359 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": 1003823, "vin": [ { "gen": { "height": 1003813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6f153b7f7312a68064ad33aaca8a794b7e4c20e5a92065968f4ee5580db2f6e" } } ], "extra": [ 1, 28, 209, 127, 78, 160, 71, 205, 101, 9, 222, 53, 246, 57, 242, 230, 157, 196, 61, 6, 210, 210, 235, 197, 123, 162, 61, 244, 50, 48, 66, 76, 63, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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