Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4fb7bc48d32bdc7684d494c0b6ba4a2cae07dba1aee648830d0f7c95ad0cfe7

Tx prefix hash: a028437f9b460cb0db4eae8d83059038ef1ee644ae5b3d949eefb4a25c0e97d3
Tx public key: a0a5a0b0e38608d8ba1bed36d6cb60262bd5cf3ed7e078f76637e17cb82a6133
Timestamp: 1726547802 Timestamp [UCT]: 2024-09-17 04:36:42 Age [y:d:h:m:s]: 00:199:12:08:40
Block: 1111837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142416 RingCT/type: yes/0
Extra: 01a0a5a0b0e38608d8ba1bed36d6cb60262bd5cf3ed7e078f76637e17cb82a613302110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5284484e3e9e40148e0b021f9c4ad225de95d356f10700a25fb0949634d39487 0.600000000000 1590940 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": 1111847, "vin": [ { "gen": { "height": 1111837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5284484e3e9e40148e0b021f9c4ad225de95d356f10700a25fb0949634d39487" } } ], "extra": [ 1, 160, 165, 160, 176, 227, 134, 8, 216, 186, 27, 237, 54, 214, 203, 96, 38, 43, 213, 207, 62, 215, 224, 120, 247, 102, 55, 225, 124, 184, 42, 97, 51, 2, 17, 0, 0, 0, 8, 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