Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb5ee4c86183fb426fdeef62381a65f6452db31f121d0e758be37cd53c72200a

Tx prefix hash: f4a5cada016fcb3d7f776fb9cd3e50f25e32c85e01b76be5ee37a90caae302bc
Tx public key: f2c1428436ef7c2af8ae95a996bf1d5160c5b1c47c169e0649d6e0ed1cf40082
Timestamp: 1729972954 Timestamp [UCT]: 2024-10-26 20:02:34 Age [y:d:h:m:s]: 00:156:14:25:47
Block: 1140214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111697 RingCT/type: yes/0
Extra: 01f2c1428436ef7c2af8ae95a996bf1d5160c5b1c47c169e0649d6e0ed1cf400820211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dedace1343dcde9ee8b82d19d879813019e3429f8d46b2952d71231ec45f7b44 0.600000000000 1624009 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": 1140224, "vin": [ { "gen": { "height": 1140214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dedace1343dcde9ee8b82d19d879813019e3429f8d46b2952d71231ec45f7b44" } } ], "extra": [ 1, 242, 193, 66, 132, 54, 239, 124, 42, 248, 174, 149, 169, 150, 191, 29, 81, 96, 197, 177, 196, 124, 22, 158, 6, 73, 214, 224, 237, 28, 244, 0, 130, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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