Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8051f61c2364f7def5f1efb6b33f6c60264a535afc3e2169c85f4664455b074

Tx prefix hash: f2c07ead4627fc7e84b717bad1bae74d904f2ca7d054a06b9cf7793fb8e93dca
Tx public key: 72a7ceb5514b4914407eb57d3c5788b668516c33f8b560d26f6ef266e4211a16
Timestamp: 1680990261 Timestamp [UCT]: 2023-04-08 21:44:21 Age [y:d:h:m:s]: 02:037:18:31:40
Block: 734437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549129 RingCT/type: yes/0
Extra: 0172a7ceb5514b4914407eb57d3c5788b668516c33f8b560d26f6ef266e4211a160211000000035029cbac000000000000000000

1 output(s) for total of 2.262067529000 dcy

stealth address amount amount idx
00: 46a2caa5c3a9c6d518e888d5fd0256141b7ebb78c34f1f3c254d9abe8842e05c 2.262067529000 1180640 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": 734447, "vin": [ { "gen": { "height": 734437 } } ], "vout": [ { "amount": 2262067529, "target": { "key": "46a2caa5c3a9c6d518e888d5fd0256141b7ebb78c34f1f3c254d9abe8842e05c" } } ], "extra": [ 1, 114, 167, 206, 181, 81, 75, 73, 20, 64, 126, 181, 125, 60, 87, 136, 182, 104, 81, 108, 51, 248, 181, 96, 210, 111, 110, 242, 102, 228, 33, 26, 22, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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