Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b64ddc4880c1d525a27fa9e3f792904caf7c3e17a8c9e8113cb5096d839b3d39

Tx prefix hash: 0c1c3c191452c142de55701b822856963c835d927523dd7ec8c4b57fe12bea67
Tx public key: 4e6872bc7143ac08afa5678d01ead166dca6bd8db1c9e51967a02a68a6b77de3
Timestamp: 1729532814 Timestamp [UCT]: 2024-10-21 17:46:54 Age [y:d:h:m:s]: 00:143:16:14:23
Block: 1136550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102500 RingCT/type: yes/0
Extra: 014e6872bc7143ac08afa5678d01ead166dca6bd8db1c9e51967a02a68a6b77de30211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5076dc444d8ac42e47d2c937201903d5dfcdfdebbd4f3530023f7cd9f6c9909 0.600000000000 1619897 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": 1136560, "vin": [ { "gen": { "height": 1136550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5076dc444d8ac42e47d2c937201903d5dfcdfdebbd4f3530023f7cd9f6c9909" } } ], "extra": [ 1, 78, 104, 114, 188, 113, 67, 172, 8, 175, 165, 103, 141, 1, 234, 209, 102, 220, 166, 189, 141, 177, 201, 229, 25, 103, 160, 42, 104, 166, 183, 125, 227, 2, 17, 0, 0, 0, 3, 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