Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 722f969e32ed0c87cb213b72dcacd2d88ea8d36e4a542d8edb8b79807f5c4d8c

Tx prefix hash: 109fc100fc5b6f8cb933b0af9ff14fd667e06882d4a2246b40bd736979473582
Tx public key: 35e559c7fc32f185d9ab7dcf9d5251140243d2e8419179de767e26e2894a52b4
Timestamp: 1724001637 Timestamp [UCT]: 2024-08-18 17:20:37 Age [y:d:h:m:s]: 00:236:17:04:42
Block: 1090735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169047 RingCT/type: yes/0
Extra: 0135e559c7fc32f185d9ab7dcf9d5251140243d2e8419179de767e26e2894a52b402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e11fde3aff90c8568915b0dee825ba503e0875d750a47b8f926b51d598d8ea3 0.600000000000 1565358 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": 1090745, "vin": [ { "gen": { "height": 1090735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e11fde3aff90c8568915b0dee825ba503e0875d750a47b8f926b51d598d8ea3" } } ], "extra": [ 1, 53, 229, 89, 199, 252, 50, 241, 133, 217, 171, 125, 207, 157, 82, 81, 20, 2, 67, 210, 232, 65, 145, 121, 222, 118, 126, 38, 226, 137, 74, 82, 180, 2, 17, 0, 0, 0, 2, 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