Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28ce10019e52b5b427df430c4c12f9955c1fd898c0fe469b41c934f1f7cfaa09

Tx prefix hash: 531ef76f9b2f9f4085b85c2604982295b2baeecfe1820ef57e5da840df7b7aca
Tx public key: 1a22760e9f76d8a369b3f3ff6aa58ed57fba1beaaf30db6e48e9cab4fd6ac3fa
Timestamp: 1763165443 Timestamp [UCT]: 2025-11-15 00:10:43 Age [y:d:h:m:s]: 00:038:18:27:24
Block: 1412291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27749 RingCT/type: yes/0
Extra: 011a22760e9f76d8a369b3f3ff6aa58ed57fba1beaaf30db6e48e9cab4fd6ac3fa021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37dbd930aa1535671898f2c0242fbd057af0d1eb83aa6cbd77e5b50abd2a0727 0.600000000000 1900758 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": 1412301, "vin": [ { "gen": { "height": 1412291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37dbd930aa1535671898f2c0242fbd057af0d1eb83aa6cbd77e5b50abd2a0727" } } ], "extra": [ 1, 26, 34, 118, 14, 159, 118, 216, 163, 105, 179, 243, 255, 106, 165, 142, 213, 127, 186, 27, 234, 175, 48, 219, 110, 72, 233, 202, 180, 253, 106, 195, 250, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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