Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14cf5e73a84ba8f6a4befd39da6bfef509e38ae0d7972d77f937fb9ef64b1506

Tx prefix hash: 892844b0704ef668d0b383084172d403e6ee72b5b1ea7314b35f4910bf211bd8
Tx public key: fa6837ebc4aeede210cc17af293a36be9c13d3cc4e9677131c298626dc8a717b
Timestamp: 1734020484 Timestamp [UCT]: 2024-12-12 16:21:24 Age [y:d:h:m:s]: 00:092:21:01:23
Block: 1173702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66162 RingCT/type: yes/0
Extra: 01fa6837ebc4aeede210cc17af293a36be9c13d3cc4e9677131c298626dc8a717b021100000001a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cf70143ef2a78bfe4539f74404e0577cf2499b8fc28b88b8f82233289a0ef3c 0.600000000000 1659753 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": 1173712, "vin": [ { "gen": { "height": 1173702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cf70143ef2a78bfe4539f74404e0577cf2499b8fc28b88b8f82233289a0ef3c" } } ], "extra": [ 1, 250, 104, 55, 235, 196, 174, 237, 226, 16, 204, 23, 175, 41, 58, 54, 190, 156, 19, 211, 204, 78, 150, 119, 19, 28, 41, 134, 38, 220, 138, 113, 123, 2, 17, 0, 0, 0, 1, 162, 215, 95, 68, 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