Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e95db4deeec8bc5531bd8e6cf8ecaffd435f74b81f640324ed1f7b82f15de94

Tx prefix hash: 7f999450ef3ea021b175fc95c7d96956d1198437d252b1732b21f306d29f23bd
Tx public key: 1e329cea06be5ceb03b2eb5526f6d16e89d52e0101b96b58c77460d1b87ae333
Timestamp: 1722693833 Timestamp [UCT]: 2024-08-03 14:03:53 Age [y:d:h:m:s]: 00:246:11:11:51
Block: 1079882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176040 RingCT/type: yes/0
Extra: 011e329cea06be5ceb03b2eb5526f6d16e89d52e0101b96b58c77460d1b87ae33302110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a7013bb94d6be37eef9f9e55b95fb8b80545ae1840b573079f7c163fc8336ae 0.600000000000 1553027 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": 1079892, "vin": [ { "gen": { "height": 1079882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a7013bb94d6be37eef9f9e55b95fb8b80545ae1840b573079f7c163fc8336ae" } } ], "extra": [ 1, 30, 50, 156, 234, 6, 190, 92, 235, 3, 178, 235, 85, 38, 246, 209, 110, 137, 213, 46, 1, 1, 185, 107, 88, 199, 116, 96, 209, 184, 122, 227, 51, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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