Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 395555d1b37f2ec4c30e4cd6dceedf1ee474a40d6b6028718e0b4bc11d50cea1

Tx prefix hash: c9ad3882800c5fef66470b147850ad911423adacbdc119099f9d75952d3f914f
Tx public key: 8370780a86f47e55a86d764ec6b49aff672a7d719df9981f0f10fe6779c43d4d
Timestamp: 1704079455 Timestamp [UCT]: 2024-01-01 03:24:15 Age [y:d:h:m:s]: 00:318:22:10:37
Block: 925558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228359 RingCT/type: yes/0
Extra: 018370780a86f47e55a86d764ec6b49aff672a7d719df9981f0f10fe6779c43d4d02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38ceee110c6f6fe8c3d8ae8e5f33d2de1169169109e0cd8ab0a7195d93d35d32 0.600000000000 1383322 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": 925568, "vin": [ { "gen": { "height": 925558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38ceee110c6f6fe8c3d8ae8e5f33d2de1169169109e0cd8ab0a7195d93d35d32" } } ], "extra": [ 1, 131, 112, 120, 10, 134, 244, 126, 85, 168, 109, 118, 78, 198, 180, 154, 255, 103, 42, 125, 113, 157, 249, 152, 31, 15, 16, 254, 103, 121, 196, 61, 77, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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