Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 120d4e624e43f23a366baf1ab2ed27585108024bd4f225defea2d90e6f44c707

Tx prefix hash: 8620f0904014bd9301b78ef690f3183b0de3b3d61ea1e86d19c2b675d84af950
Tx public key: 0c4a40e1fe1608b0270c8c95c5070d6106efe8b1d5e43f4a3d414ad1259c2733
Timestamp: 1724537304 Timestamp [UCT]: 2024-08-24 22:08:24 Age [y:d:h:m:s]: 00:215:04:45:59
Block: 1095193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153637 RingCT/type: yes/0
Extra: 010c4a40e1fe1608b0270c8c95c5070d6106efe8b1d5e43f4a3d414ad1259c2733021100000001e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce1db7e9ea886b46552ee70a58699462a6663959b41c1a775e847bcfb060d610 0.600000000000 1570344 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": 1095203, "vin": [ { "gen": { "height": 1095193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce1db7e9ea886b46552ee70a58699462a6663959b41c1a775e847bcfb060d610" } } ], "extra": [ 1, 12, 74, 64, 225, 254, 22, 8, 176, 39, 12, 140, 149, 197, 7, 13, 97, 6, 239, 232, 177, 213, 228, 63, 74, 61, 65, 74, 209, 37, 156, 39, 51, 2, 17, 0, 0, 0, 1, 227, 55, 53, 142, 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