Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a3524684b3553e934d1d4b8d23f62771aa46bb202fce344ba5397e2bf3e9c66

Tx prefix hash: f20d4a594ea504c001a3668601f5cb15b9538793b5ebab16c50f1c727116cf90
Tx public key: c6691194e50a531f80a8d15ce05231b8fc84b0a650e57d35ce8f85088ef6b24a
Timestamp: 1714357650 Timestamp [UCT]: 2024-04-29 02:27:30 Age [y:d:h:m:s]: 00:200:00:00:26
Block: 1010778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143155 RingCT/type: yes/0
Extra: 01c6691194e50a531f80a8d15ce05231b8fc84b0a650e57d35ce8f85088ef6b24a02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 592134a83960780b8f0861ce8e86f7ff225f48edc17c0aab1ab3fdde065de8e4 0.600000000000 1472826 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": 1010788, "vin": [ { "gen": { "height": 1010778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "592134a83960780b8f0861ce8e86f7ff225f48edc17c0aab1ab3fdde065de8e4" } } ], "extra": [ 1, 198, 105, 17, 148, 229, 10, 83, 31, 128, 168, 209, 92, 224, 82, 49, 184, 252, 132, 176, 166, 80, 229, 125, 53, 206, 143, 133, 8, 142, 246, 178, 74, 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