Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cdbdd21fd145c294813f69d5d54538847627fdaafaa157cf12c1eff36e8ddd6

Tx prefix hash: 6f76a2b649596430c6dcbe73fe90d1dc8816a1e3a343e157310dfd369ed2bcab
Tx public key: f326c248caf4de0ea440cf71971f983d2b5f06539281aa51daa4069ae20f3115
Timestamp: 1696027049 Timestamp [UCT]: 2023-09-29 22:37:29 Age [y:d:h:m:s]: 01:172:12:05:14
Block: 859017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384354 RingCT/type: yes/0
Extra: 01f326c248caf4de0ea440cf71971f983d2b5f06539281aa51daa4069ae20f3115021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.874420091000 dcy

stealth address amount amount idx
00: 0dde9ec4b470fd28b9941975213f6643640d1cac1347dc13db06dd4479f43230 0.874420091000 1313223 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": 859027, "vin": [ { "gen": { "height": 859017 } } ], "vout": [ { "amount": 874420091, "target": { "key": "0dde9ec4b470fd28b9941975213f6643640d1cac1347dc13db06dd4479f43230" } } ], "extra": [ 1, 243, 38, 194, 72, 202, 244, 222, 14, 164, 64, 207, 113, 151, 31, 152, 61, 43, 95, 6, 83, 146, 129, 170, 81, 218, 164, 6, 154, 226, 15, 49, 21, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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