Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f60b04238b037c5e7d5620e00e9227ab05d2a32fb72a61d710d8dcaba934e04

Tx prefix hash: bc5db9ba6e9eedd0e4b351e52bb70cd64fb1a2b2edaff00f83544c877a1e81db
Tx public key: 1a48646874493a2cb98da4e7aca93c4e0af7bb16e62aa8b1ecdc6e187add78a8
Timestamp: 1724080524 Timestamp [UCT]: 2024-08-19 15:15:24 Age [y:d:h:m:s]: 00:230:06:14:45
Block: 1091390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164417 RingCT/type: yes/0
Extra: 011a48646874493a2cb98da4e7aca93c4e0af7bb16e62aa8b1ecdc6e187add78a802110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07c3f5ff848cf9a386dc884495115f9fead673ecdf196c6ae0d7f80b34400f5b 0.600000000000 1566021 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": 1091400, "vin": [ { "gen": { "height": 1091390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07c3f5ff848cf9a386dc884495115f9fead673ecdf196c6ae0d7f80b34400f5b" } } ], "extra": [ 1, 26, 72, 100, 104, 116, 73, 58, 44, 185, 141, 164, 231, 172, 169, 60, 78, 10, 247, 187, 22, 230, 42, 168, 177, 236, 220, 110, 24, 122, 221, 120, 168, 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