Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2628c178b4e5be1257537c65f8435b23e2ac872144f06c2b5d25c155c694fe72

Tx prefix hash: 62c1d273502591afe3ada3e563fcac995c88d77f5e0e12b9549d6adb9fc806b0
Tx public key: 1a7db8fd96dbdba1ed2331545ec598d18e53f9d2e1d3d73e8a0b69142a0da227
Timestamp: 1762670494 Timestamp [UCT]: 2025-11-09 06:41:34 Age [y:d:h:m:s]: 00:011:19:03:50
Block: 1408191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8431 RingCT/type: yes/0
Extra: 011a7db8fd96dbdba1ed2331545ec598d18e53f9d2e1d3d73e8a0b69142a0da2270211000000048368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb28763406bd19d5c0a9b40acf0db6bd74e7c46840344aa5c9e63371f05765ba 0.600000000000 1896618 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": 1408201, "vin": [ { "gen": { "height": 1408191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb28763406bd19d5c0a9b40acf0db6bd74e7c46840344aa5c9e63371f05765ba" } } ], "extra": [ 1, 26, 125, 184, 253, 150, 219, 219, 161, 237, 35, 49, 84, 94, 197, 152, 209, 142, 83, 249, 210, 225, 211, 215, 62, 138, 11, 105, 20, 42, 13, 162, 39, 2, 17, 0, 0, 0, 4, 131, 104, 38, 109, 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