Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92fba8d7d3c905385be74a3d1042f736a154ef91a9302985112d6f7abe3e17e4

Tx prefix hash: 7f04d8ca65c864cf7d16bf879695be928503f64b936f8249f0c7985860280747
Tx public key: d6aa64cf60294a047ed99cff7906b95c6f6a6846f707a51ca356157e5da3a9b6
Timestamp: 1681733422 Timestamp [UCT]: 2023-04-17 12:10:22 Age [y:d:h:m:s]: 01:353:08:25:22
Block: 740547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513810 RingCT/type: yes/0
Extra: 01d6aa64cf60294a047ed99cff7906b95c6f6a6846f707a51ca356157e5da3a9b602110000000483600029000000000000000000

1 output(s) for total of 2.159039512000 dcy

stealth address amount amount idx
00: 67deb07c57f5da7da4aa4f72673a019c16c7ed40b9f7dd4df9a06baa2b14c4d7 2.159039512000 1187444 of 0

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": 740557, "vin": [ { "gen": { "height": 740547 } } ], "vout": [ { "amount": 2159039512, "target": { "key": "67deb07c57f5da7da4aa4f72673a019c16c7ed40b9f7dd4df9a06baa2b14c4d7" } } ], "extra": [ 1, 214, 170, 100, 207, 96, 41, 74, 4, 126, 217, 156, 255, 121, 6, 185, 92, 111, 106, 104, 70, 247, 7, 165, 28, 163, 86, 21, 126, 93, 163, 169, 182, 2, 17, 0, 0, 0, 4, 131, 96, 0, 41, 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