Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b62e55a11f21a7f83dc52c13652a1f133eca8c36bf032bc3023636270dc769e5

Tx prefix hash: 7b0684213e2ad0416a47834f9e46886550e4116a96076117061b7ff5f58bd629
Tx public key: 40879caab35bde4d9238f3ae4b75c60b3f42fbad03e9e87b32f4b3f69f408202
Timestamp: 1717507667 Timestamp [UCT]: 2024-06-04 13:27:47 Age [y:d:h:m:s]: 01:126:02:51:35
Block: 1036902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348660 RingCT/type: yes/0
Extra: 0140879caab35bde4d9238f3ae4b75c60b3f42fbad03e9e87b32f4b3f69f4082020211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8de2700a0bde093008178b5cd7c33618da7b4590a72385162d25909d7e09c23 0.600000000000 1505433 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": 1036912, "vin": [ { "gen": { "height": 1036902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8de2700a0bde093008178b5cd7c33618da7b4590a72385162d25909d7e09c23" } } ], "extra": [ 1, 64, 135, 156, 170, 179, 91, 222, 77, 146, 56, 243, 174, 75, 117, 198, 11, 63, 66, 251, 173, 3, 233, 232, 123, 50, 244, 179, 246, 159, 64, 130, 2, 2, 17, 0, 0, 0, 1, 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