Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1e84b86db266d0f21545c1188f7d26bd475acc8a2f8185b6f4d80e86c30c670

Tx prefix hash: 9bd5ffaeb3c705e52fdb0f7f81c20e33a606fbc2a797488a911631312e166fc1
Tx public key: 89cb245a366e6aa066c8211ff167e81d22b492558d49d81895b265cf79e86f3d
Timestamp: 1705688520 Timestamp [UCT]: 2024-01-19 18:22:00 Age [y:d:h:m:s]: 01:152:08:25:44
Block: 938878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369895 RingCT/type: yes/0
Extra: 0189cb245a366e6aa066c8211ff167e81d22b492558d49d81895b265cf79e86f3d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45596a4ab57299d871fab99f443aa980a48847bb7e8a62b2bacdf41309d7e749 0.600000000000 1396960 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": 938888, "vin": [ { "gen": { "height": 938878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45596a4ab57299d871fab99f443aa980a48847bb7e8a62b2bacdf41309d7e749" } } ], "extra": [ 1, 137, 203, 36, 90, 54, 110, 106, 160, 102, 200, 33, 31, 241, 103, 232, 29, 34, 180, 146, 85, 141, 73, 216, 24, 149, 178, 101, 207, 121, 232, 111, 61, 2, 17, 0, 0, 0, 3, 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