Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7f7da8847e1da4e302dee7eafec050f7ef32369faec72d16de428001d115889

Tx prefix hash: c641bd3ac40318a7aa22a1a67980003887b2f9f4a93510804a958959c3ebf3d0
Tx public key: 91e00f0b2dcedb197e777e57ec250b276fd7ba47ebd815d392341c6f09f15faf
Timestamp: 1707493984 Timestamp [UCT]: 2024-02-09 15:53:04 Age [y:d:h:m:s]: 00:339:19:48:46
Block: 953861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243283 RingCT/type: yes/0
Extra: 0191e00f0b2dcedb197e777e57ec250b276fd7ba47ebd815d392341c6f09f15faf0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 864cba8c20e590b991bd84d6a564ca0ef5777998016f9eb9959aa10a769bd12d 0.600000000000 1413129 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": 953871, "vin": [ { "gen": { "height": 953861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "864cba8c20e590b991bd84d6a564ca0ef5777998016f9eb9959aa10a769bd12d" } } ], "extra": [ 1, 145, 224, 15, 11, 45, 206, 219, 25, 126, 119, 126, 87, 236, 37, 11, 39, 111, 215, 186, 71, 235, 216, 21, 211, 146, 52, 28, 111, 9, 241, 95, 175, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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