Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a2fb95e229f9eea3ea2c6839b5012fac4c0470c31d107f97329304a92c8269e

Tx prefix hash: 4ada633189bd17cf79ead53b8c1b4d046ff59d2d563c51a9293e083719c4498f
Tx public key: 890e98e4d7db4f76f3a04f2ae8e8302a2c2f37b27150dc7a39d4acbbf719d1d2
Timestamp: 1733147178 Timestamp [UCT]: 2024-12-02 13:46:18 Age [y:d:h:m:s]: 00:110:17:08:58
Block: 1166449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78928 RingCT/type: yes/0
Extra: 01890e98e4d7db4f76f3a04f2ae8e8302a2c2f37b27150dc7a39d4acbbf719d1d2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f50dcf18ec77086d7ec829f0914d1f68144f752662737b84d907df33edc22bdd 0.600000000000 1652136 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": 1166459, "vin": [ { "gen": { "height": 1166449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f50dcf18ec77086d7ec829f0914d1f68144f752662737b84d907df33edc22bdd" } } ], "extra": [ 1, 137, 14, 152, 228, 215, 219, 79, 118, 243, 160, 79, 42, 232, 232, 48, 42, 44, 47, 55, 178, 113, 80, 220, 122, 57, 212, 172, 187, 247, 25, 209, 210, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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