Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62700fa297c3bb0e718feed4e1f7205d01c5a743984a15589d7223a814bd4e09

Tx prefix hash: 7473ea960902f8f145d17754c5054f50715619d71e1f73cefadf1414ba1ef83d
Tx public key: fe60f1638eb8b400a1e6197d2d4ae7297e43a360dd0d4c55af16d91de8bf4de8
Timestamp: 1721278300 Timestamp [UCT]: 2024-07-18 04:51:40 Age [y:d:h:m:s]: 00:256:14:58:11
Block: 1068170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183310 RingCT/type: yes/0
Extra: 01fe60f1638eb8b400a1e6197d2d4ae7297e43a360dd0d4c55af16d91de8bf4de802110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: def9c0dcd0a68e34a8df1274c4d479cac83c3ec863bebd8f193fdcc97d5c177c 0.600000000000 1539215 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": 1068180, "vin": [ { "gen": { "height": 1068170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "def9c0dcd0a68e34a8df1274c4d479cac83c3ec863bebd8f193fdcc97d5c177c" } } ], "extra": [ 1, 254, 96, 241, 99, 142, 184, 180, 0, 161, 230, 25, 125, 45, 74, 231, 41, 126, 67, 163, 96, 221, 13, 76, 85, 175, 22, 217, 29, 232, 191, 77, 232, 2, 17, 0, 0, 0, 14, 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