Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 199feef38db65046b65d26e049be123b08048e538fbe3dad94ff438751d205a5

Tx prefix hash: d42f4301779b6fa0ff28c0e63bef8b63c7831235cde27fc96e9f13e968b16326
Tx public key: 9c6f04970fd8e2cc7a4265ad508eef9f7347836059ac3e7c9c9e707e3c74e6f7
Timestamp: 1722960173 Timestamp [UCT]: 2024-08-06 16:02:53 Age [y:d:h:m:s]: 00:200:22:00:30
Block: 1082085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143454 RingCT/type: yes/0
Extra: 019c6f04970fd8e2cc7a4265ad508eef9f7347836059ac3e7c9c9e707e3c74e6f702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e5014ba4ac311ae073e389c736ae63c7abde04cd72373e3ad580b045fe536be 0.600000000000 1555908 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": 1082095, "vin": [ { "gen": { "height": 1082085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e5014ba4ac311ae073e389c736ae63c7abde04cd72373e3ad580b045fe536be" } } ], "extra": [ 1, 156, 111, 4, 151, 15, 216, 226, 204, 122, 66, 101, 173, 80, 142, 239, 159, 115, 71, 131, 96, 89, 172, 62, 124, 156, 158, 112, 126, 60, 116, 230, 247, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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