Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc4e66593998478a5d2731c3ffcf8f54ebffdcd1ab47557f4f927aaff342f2f2

Tx prefix hash: fd8c3640cdd1ee2d6f103d9ed379fa6e49c50d3c3987d64b85f07f72d293bc18
Tx public key: 9e07d3023d8c5b1a11c00684055cd8de15ed1b628b890ab572884da0bcf871dc
Timestamp: 1718900431 Timestamp [UCT]: 2024-06-20 16:20:31 Age [y:d:h:m:s]: 00:289:11:05:11
Block: 1048444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206833 RingCT/type: yes/0
Extra: 019e07d3023d8c5b1a11c00684055cd8de15ed1b628b890ab572884da0bcf871dc0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 512509007d51dee41d86e0be232e05ed4abdc7f8e9c13b4fac148eaab2dd1384 0.600000000000 1518529 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": 1048454, "vin": [ { "gen": { "height": 1048444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "512509007d51dee41d86e0be232e05ed4abdc7f8e9c13b4fac148eaab2dd1384" } } ], "extra": [ 1, 158, 7, 211, 2, 61, 140, 91, 26, 17, 192, 6, 132, 5, 92, 216, 222, 21, 237, 27, 98, 139, 137, 10, 181, 114, 136, 77, 160, 188, 248, 113, 220, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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