Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84550afc1638c61e18a54ca0a04ed112f4bd46dc4dd1bb2515578cd5365c2189

Tx prefix hash: ecc0a887d1053acc3d2030da79b5fa3ab59dce53509dc578d6fd0c34376839e1
Tx public key: 609aafeeb0e31f281cf05f933be0ca8ae2b9ad462243c7c3540b25f154850fc3
Timestamp: 1706990843 Timestamp [UCT]: 2024-02-03 20:07:23 Age [y:d:h:m:s]: 01:040:04:35:35
Block: 949692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289791 RingCT/type: yes/0
Extra: 01609aafeeb0e31f281cf05f933be0ca8ae2b9ad462243c7c3540b25f154850fc302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0703dbd35830b21b95c22c2e6c8b22e65c0ff8fb657cc59288ae0837770a418 0.600000000000 1408222 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": 949702, "vin": [ { "gen": { "height": 949692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0703dbd35830b21b95c22c2e6c8b22e65c0ff8fb657cc59288ae0837770a418" } } ], "extra": [ 1, 96, 154, 175, 238, 176, 227, 31, 40, 28, 240, 95, 147, 59, 224, 202, 138, 226, 185, 173, 70, 34, 67, 199, 195, 84, 11, 37, 241, 84, 133, 15, 195, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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