Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b3301f220b3bae528c61e12a96c2ff0ea06580bc95a297179cdf6a6c235eac8

Tx prefix hash: e16c1dab20d79efd440e46f734057c3d113c538fc45e6ee0f021b209dfd46f4b
Tx public key: 4ffa8fc39c8fa18821e3941bbbe9d26a9d49ac2e9e6124535229c9ebd76e6a45
Timestamp: 1718738758 Timestamp [UCT]: 2024-06-18 19:25:58 Age [y:d:h:m:s]: 00:362:02:22:48
Block: 1047093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258713 RingCT/type: yes/0
Extra: 014ffa8fc39c8fa18821e3941bbbe9d26a9d49ac2e9e6124535229c9ebd76e6a4502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 163a61093715f506a611509fb553114f2b1504cd4cfaf8d53dc9c37435d552e2 0.600000000000 1516912 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": 1047103, "vin": [ { "gen": { "height": 1047093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "163a61093715f506a611509fb553114f2b1504cd4cfaf8d53dc9c37435d552e2" } } ], "extra": [ 1, 79, 250, 143, 195, 156, 143, 161, 136, 33, 227, 148, 27, 187, 233, 210, 106, 157, 73, 172, 46, 158, 97, 36, 83, 82, 41, 201, 235, 215, 110, 106, 69, 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