Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d60641b9d8cdaef1e393fcc4be4dcc835dbc69cb62158caf7684d42b66848ed

Tx prefix hash: 2282a348a8a619e3e35e40a49de1b391614ea812f08b2bbb272061dbef3dc173
Tx public key: 2c0dd2c0cd7d5fa0100975627fc24facbbb6d5c8454a1f65096ba8d612030fb6
Timestamp: 1728418216 Timestamp [UCT]: 2024-10-08 20:10:16 Age [y:d:h:m:s]: 00:173:17:33:19
Block: 1127350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123947 RingCT/type: yes/0
Extra: 012c0dd2c0cd7d5fa0100975627fc24facbbb6d5c8454a1f65096ba8d612030fb6021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94e342794a6c2ea41396200c944523c160679ca1165a4fc7c8d7f41a5f880d3a 0.600000000000 1610153 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": 1127360, "vin": [ { "gen": { "height": 1127350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94e342794a6c2ea41396200c944523c160679ca1165a4fc7c8d7f41a5f880d3a" } } ], "extra": [ 1, 44, 13, 210, 192, 205, 125, 95, 160, 16, 9, 117, 98, 127, 194, 79, 172, 187, 182, 213, 200, 69, 74, 31, 101, 9, 107, 168, 214, 18, 3, 15, 182, 2, 17, 0, 0, 0, 1, 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