Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 547c004af912e2192f50eac93b8d41b37d88d4a25fd07733d0618b3abc3c14f6

Tx prefix hash: b6e68479425b98d9816b48cabd85c69ef417fc6edd0a771f79eef4da101edef4
Tx public key: aca126237c9b5c55a21eb4cb9b800d9bd23fe6ebe762ab40ab783243c5f4f63a
Timestamp: 1733212444 Timestamp [UCT]: 2024-12-03 07:54:04 Age [y:d:h:m:s]: 00:116:05:28:38
Block: 1166991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82862 RingCT/type: yes/0
Extra: 01aca126237c9b5c55a21eb4cb9b800d9bd23fe6ebe762ab40ab783243c5f4f63a021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4e91ca9a23f703e623c7ef596f80182d3417237249d24d84518bd10672b54dc 0.600000000000 1652684 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": 1167001, "vin": [ { "gen": { "height": 1166991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4e91ca9a23f703e623c7ef596f80182d3417237249d24d84518bd10672b54dc" } } ], "extra": [ 1, 172, 161, 38, 35, 124, 155, 92, 85, 162, 30, 180, 203, 155, 128, 13, 155, 210, 63, 230, 235, 231, 98, 171, 64, 171, 120, 50, 67, 197, 244, 246, 58, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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