Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a171dd53c20464e946c0eb89fc8f7ea777c5fd6196098003ce3d097f9a3d656

Tx prefix hash: bf71af0243e4934a587553f8c9aaba0e74c9a6fb9aa16cbc060b46a9c9506178
Tx public key: 3df81d2060849ad231ee8c1fde221f4f84ceed9fe5473e657c1bd9e733413297
Timestamp: 1727201441 Timestamp [UCT]: 2024-09-24 18:10:41 Age [y:d:h:m:s]: 00:060:16:22:33
Block: 1117261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43363 RingCT/type: yes/0
Extra: 013df81d2060849ad231ee8c1fde221f4f84ceed9fe5473e657c1bd9e73341329702110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55943bb19a1d44c21f3acf7dfdeac2ba6d84a6f133ae316fd6a8896710a99b01 0.600000000000 1598034 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": 1117271, "vin": [ { "gen": { "height": 1117261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55943bb19a1d44c21f3acf7dfdeac2ba6d84a6f133ae316fd6a8896710a99b01" } } ], "extra": [ 1, 61, 248, 29, 32, 96, 132, 154, 210, 49, 238, 140, 31, 222, 34, 31, 79, 132, 206, 237, 159, 229, 71, 62, 101, 124, 27, 217, 231, 51, 65, 50, 151, 2, 17, 0, 0, 0, 12, 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