Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 189f9efe73b8dbe9f14d9fd8e52f76b16701248ebe300a5484f83dcf28fcdb65

Tx prefix hash: dff367af4caea90457e7ec11bbdaa9fcc9a43cfa53305f685be5872393d5954d
Tx public key: f6135aa7573ed6b5458ecc89c9c330ad1d6ec852e1db2ae80d4fe6badf56a33e
Timestamp: 1724334125 Timestamp [UCT]: 2024-08-22 13:42:05 Age [y:d:h:m:s]: 00:299:02:39:28
Block: 1093499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213561 RingCT/type: yes/0
Extra: 01f6135aa7573ed6b5458ecc89c9c330ad1d6ec852e1db2ae80d4fe6badf56a33e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0007fd85f93b2bb643a4b64f6861e83f0186655aeea72f114f8003c378a64c5 0.600000000000 1568456 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": 1093509, "vin": [ { "gen": { "height": 1093499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0007fd85f93b2bb643a4b64f6861e83f0186655aeea72f114f8003c378a64c5" } } ], "extra": [ 1, 246, 19, 90, 167, 87, 62, 214, 181, 69, 142, 204, 137, 201, 195, 48, 173, 29, 110, 200, 82, 225, 219, 42, 232, 13, 79, 230, 186, 223, 86, 163, 62, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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