Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c278ca5b578b9c2b6be9f23eaf9e39da992a2f288c3c7a11015de5107866715b

Tx prefix hash: 1938e2b8e1aced3ad948b697b8d8dbd35559a35248585d1ce12837c4fe7ecd3b
Tx public key: e5f657e9434fb6bc3af796286bf0063ce254bba1a8f089099dcb2a175618b97e
Timestamp: 1747174995 Timestamp [UCT]: 2025-05-13 22:23:15 Age [y:d:h:m:s]: 00:186:06:07:50
Block: 1282318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130821 RingCT/type: yes/0
Extra: 01e5f657e9434fb6bc3af796286bf0063ce254bba1a8f089099dcb2a175618b97e0211000000051f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81ac732e9acf2c01f48cadee79d109c88a08fe01decc1b213de95edece8ce033 0.600000000000 1769725 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": 1282328, "vin": [ { "gen": { "height": 1282318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81ac732e9acf2c01f48cadee79d109c88a08fe01decc1b213de95edece8ce033" } } ], "extra": [ 1, 229, 246, 87, 233, 67, 79, 182, 188, 58, 247, 150, 40, 107, 240, 6, 60, 226, 84, 187, 161, 168, 240, 137, 9, 157, 203, 42, 23, 86, 24, 185, 126, 2, 17, 0, 0, 0, 5, 31, 144, 81, 122, 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