Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ce7a95ba6c01113d5cd20ee57843e562a5a6f1989533c984ec7b02e83b80d25

Tx prefix hash: e06e4a377b30a83b3eaaf3300ee9e135812a142ba6644174a291b85a39636b1e
Tx public key: e7f46a7b5b4f433a62e6397903d7e7ee420f4d77f47d392c37073ae1704e65c5
Timestamp: 1730864590 Timestamp [UCT]: 2024-11-06 03:43:10 Age [y:d:h:m:s]: 00:131:08:43:23
Block: 1147535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93734 RingCT/type: yes/0
Extra: 01e7f46a7b5b4f433a62e6397903d7e7ee420f4d77f47d392c37073ae1704e65c50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1856f996e2481860efc4b36cc23be6b62a0bb2306ce46dead9967f7b71089d35 0.600000000000 1632234 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": 1147545, "vin": [ { "gen": { "height": 1147535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1856f996e2481860efc4b36cc23be6b62a0bb2306ce46dead9967f7b71089d35" } } ], "extra": [ 1, 231, 244, 106, 123, 91, 79, 67, 58, 98, 230, 57, 121, 3, 215, 231, 238, 66, 15, 77, 119, 244, 125, 57, 44, 55, 7, 58, 225, 112, 78, 101, 197, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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