Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cb20d0d7d11910b5a5f4165da3aacf9108a0dc51be8ead0590cd617920fc5bb

Tx prefix hash: 178f662f6dca4fba60778a57e3c5d700c20fa48b0d0b99beeb0aed6a4e66f5a4
Tx public key: 273b83ed688781ee65477d7e74128978d5d3d624f0ab5817a64cb3d3c1f9f7e9
Timestamp: 1723475718 Timestamp [UCT]: 2024-08-12 15:15:18 Age [y:d:h:m:s]: 00:231:19:07:13
Block: 1086367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165542 RingCT/type: yes/0
Extra: 01273b83ed688781ee65477d7e74128978d5d3d624f0ab5817a64cb3d3c1f9f7e902110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdd22e7aade2b856285a8b55677a34577a9219ef7e0c914ee6cfd3195001dc87 0.600000000000 1560964 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": 1086377, "vin": [ { "gen": { "height": 1086367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdd22e7aade2b856285a8b55677a34577a9219ef7e0c914ee6cfd3195001dc87" } } ], "extra": [ 1, 39, 59, 131, 237, 104, 135, 129, 238, 101, 71, 125, 126, 116, 18, 137, 120, 213, 211, 214, 36, 240, 171, 88, 23, 166, 76, 179, 211, 193, 249, 247, 233, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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