Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a27f8268c287ee8a55abdb0e6e3b306e903a8147cc06db120aaaad44e886d38

Tx prefix hash: 13d23576b1be6c9ece4569dd867013e5339a38517a8145d85ac11271f4ed6c9c
Tx public key: 66c77a197e8f340eebc07031477014c21917c761e920cf9da20f488a862e607a
Timestamp: 1757600476 Timestamp [UCT]: 2025-09-11 14:21:16 Age [y:d:h:m:s]: 00:083:12:28:54
Block: 1366185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59789 RingCT/type: yes/0
Extra: 0166c77a197e8f340eebc07031477014c21917c761e920cf9da20f488a862e607a021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f034ad2b0f17994f5e33ce1e6e33c71f5f0f2efcb77d2d09ca95e5db7e8dc32 0.600000000000 1854224 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": 1366195, "vin": [ { "gen": { "height": 1366185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f034ad2b0f17994f5e33ce1e6e33c71f5f0f2efcb77d2d09ca95e5db7e8dc32" } } ], "extra": [ 1, 102, 199, 122, 25, 126, 143, 52, 14, 235, 192, 112, 49, 71, 112, 20, 194, 25, 23, 199, 97, 233, 32, 207, 157, 162, 15, 72, 138, 134, 46, 96, 122, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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