Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6708e53203d5e18c7d4f0cc1b0c0f26c5ef364b9baec877954259f24afe0ecea

Tx prefix hash: 3fa109951bc75b524e74c474637bf2a4755294b59bf44f6cfb52b8de128c7aba
Tx public key: a71e7eff9dd40ff191e0423e664002d254a5d18ad56d055815e46195994c4d52
Timestamp: 1723088665 Timestamp [UCT]: 2024-08-08 03:44:25 Age [y:d:h:m:s]: 00:241:13:41:21
Block: 1083161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172528 RingCT/type: yes/0
Extra: 01a71e7eff9dd40ff191e0423e664002d254a5d18ad56d055815e46195994c4d5202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd74a85fe9b5bdbebe3f50b0aeb8a2d5b5a1c540ad2df3afc5e195bf8c1c2712 0.600000000000 1556996 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": 1083171, "vin": [ { "gen": { "height": 1083161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd74a85fe9b5bdbebe3f50b0aeb8a2d5b5a1c540ad2df3afc5e195bf8c1c2712" } } ], "extra": [ 1, 167, 30, 126, 255, 157, 212, 15, 241, 145, 224, 66, 62, 102, 64, 2, 210, 84, 165, 209, 138, 213, 109, 5, 88, 21, 228, 97, 149, 153, 76, 77, 82, 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