Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ed9dff1ac1121cc82ee78e971ecbfa2da1f6041fb6a9ed44f2de557b3080a43

Tx prefix hash: ef4ef5f324d0f968a153cbdffbb2615c9ec5f9794fcbb6dece9c50ade6804322
Tx public key: 4543a9b02c25f6df83af6ef2844de8005771392e68cac562da4d3c3c0e9bc6f8
Timestamp: 1609183254 Timestamp [UCT]: 2020-12-28 19:20:54 Age [y:d:h:m:s]: 04:134:05:58:16
Block: 171022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1109233 RingCT/type: yes/0
Extra: 014543a9b02c25f6df83af6ef2844de8005771392e68cac562da4d3c3c0e9bc6f80211000003c4df1e48bb000000000000000000

1 output(s) for total of 166.469158306000 dcy

stealth address amount amount idx
00: 05a7ca97db50fb01eb3ab1a97c9a1397d5989c0d0f9e41dadcf6a2c74d0fd4a0 166.469158306000 321479 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": 171032, "vin": [ { "gen": { "height": 171022 } } ], "vout": [ { "amount": 166469158306, "target": { "key": "05a7ca97db50fb01eb3ab1a97c9a1397d5989c0d0f9e41dadcf6a2c74d0fd4a0" } } ], "extra": [ 1, 69, 67, 169, 176, 44, 37, 246, 223, 131, 175, 110, 242, 132, 77, 232, 0, 87, 113, 57, 46, 104, 202, 197, 98, 218, 77, 60, 60, 14, 155, 198, 248, 2, 17, 0, 0, 3, 196, 223, 30, 72, 187, 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