Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92a74b5f0a9e10495f3be41a97e45d55796224cf5eaff72bb3344506b05768c6

Tx prefix hash: 16339e6b6e8f7fe5c5fa3cf57fb52e9596d71e268bc6183109773ff5cfe99921
Tx public key: 7fbe0bced5b89f92da0b767885942cfe5367d18b30d9d98c2d1cabe27a1ead24
Timestamp: 1732385740 Timestamp [UCT]: 2024-11-23 18:15:40 Age [y:d:h:m:s]: 00:138:00:51:31
Block: 1160135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98475 RingCT/type: yes/0
Extra: 017fbe0bced5b89f92da0b767885942cfe5367d18b30d9d98c2d1cabe27a1ead24021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27dff716e018e7bc51cf28542ea291e6fbc4a089ba8b566e118d70a1c196042c 0.600000000000 1645778 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": 1160145, "vin": [ { "gen": { "height": 1160135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27dff716e018e7bc51cf28542ea291e6fbc4a089ba8b566e118d70a1c196042c" } } ], "extra": [ 1, 127, 190, 11, 206, 213, 184, 159, 146, 218, 11, 118, 120, 133, 148, 44, 254, 83, 103, 209, 139, 48, 217, 217, 140, 45, 28, 171, 226, 122, 30, 173, 36, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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