Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0db66280c10f408cdece850df8785b30bdcbe2b00f11a61c887f6dc5e15543f3

Tx prefix hash: ce98d155185481eca3124a8e1bab39a43d028aca120489eadcbdead351544498
Tx public key: 583e9b9bc78d3a8760dc7db9f297216ac0ebf0fc4de537925ae891f1a0becc87
Timestamp: 1636747108 Timestamp [UCT]: 2021-11-12 19:58:28 Age [y:d:h:m:s]: 03:182:16:10:51
Block: 373026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 908984 RingCT/type: yes/0
Extra: 01583e9b9bc78d3a8760dc7db9f297216ac0ebf0fc4de537925ae891f1a0becc870211000000074f792ffd000000000000000000

1 output(s) for total of 35.645967057000 dcy

stealth address amount amount idx
00: 5a2dd05bbc495ff9a5a42b0aee99a35b3d249ee17cae6566cf2198a61dd6ea06 35.645967057000 755474 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": 373036, "vin": [ { "gen": { "height": 373026 } } ], "vout": [ { "amount": 35645967057, "target": { "key": "5a2dd05bbc495ff9a5a42b0aee99a35b3d249ee17cae6566cf2198a61dd6ea06" } } ], "extra": [ 1, 88, 62, 155, 155, 199, 141, 58, 135, 96, 220, 125, 185, 242, 151, 33, 106, 192, 235, 240, 252, 77, 229, 55, 146, 90, 232, 145, 241, 160, 190, 204, 135, 2, 17, 0, 0, 0, 7, 79, 121, 47, 253, 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