Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba0879d409c3930a449c6ab0fd9e7d50314f1ce7bf60ad27ac2587181894207a

Tx prefix hash: 8bfa609b75122be61423b0268453fe952038afac1464b661a53a48a7ac3d3a17
Tx public key: 84b3f97cfd62309c86a61c365f17e5e6fb86cf2f7da2c6ee123bb78af824b915
Timestamp: 1723381556 Timestamp [UCT]: 2024-08-11 13:05:56 Age [y:d:h:m:s]: 00:234:10:38:59
Block: 1085595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167422 RingCT/type: yes/0
Extra: 0184b3f97cfd62309c86a61c365f17e5e6fb86cf2f7da2c6ee123bb78af824b915021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fa1f0bba52ea79bb5cce6e3a9b1be9632892bd06e1446f4615ba38aabec58ea 0.600000000000 1560182 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": 1085605, "vin": [ { "gen": { "height": 1085595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fa1f0bba52ea79bb5cce6e3a9b1be9632892bd06e1446f4615ba38aabec58ea" } } ], "extra": [ 1, 132, 179, 249, 124, 253, 98, 48, 156, 134, 166, 28, 54, 95, 23, 229, 230, 251, 134, 207, 47, 125, 162, 198, 238, 18, 59, 183, 138, 248, 36, 185, 21, 2, 17, 0, 0, 0, 8, 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