Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2e783634b484b01840c882d1f66bee6e1416d674163073c78dfb1cc36de7cc1

Tx prefix hash: ec0d7dff7fbec6b3a6c6b0bc56a8d6032f2787045e6434a75de1ee9fdb5c3317
Tx public key: ca1a2c9ccd127f7e94faa50c0f2c841cd2f81ff185dcf0119237db79d13bbc12
Timestamp: 1703371171 Timestamp [UCT]: 2023-12-23 22:39:31 Age [y:d:h:m:s]: 01:323:06:04:23
Block: 919687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489872 RingCT/type: yes/0
Extra: 01ca1a2c9ccd127f7e94faa50c0f2c841cd2f81ff185dcf0119237db79d13bbc1202110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c45ff5209d398893104b8089d4d17da8d8502a3ea466221cd7ff082359bc972 0.600000000000 1377363 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": 919697, "vin": [ { "gen": { "height": 919687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c45ff5209d398893104b8089d4d17da8d8502a3ea466221cd7ff082359bc972" } } ], "extra": [ 1, 202, 26, 44, 156, 205, 18, 127, 126, 148, 250, 165, 12, 15, 44, 132, 28, 210, 248, 31, 241, 133, 220, 240, 17, 146, 55, 219, 121, 209, 59, 188, 18, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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