Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e269f585a781cd77bbcfa421d09d04b81bd63fdec2a8ecf8cf04b4af9993ebaf

Tx prefix hash: 27751b87c2b9f78903681fa37f45e2dfee019732739e9dc83f0ddfffe7d50017
Tx public key: 34c6fafde80c8b9174bd50bef2e836c3020dde138a6d3b0c88e2b6049e721e01
Timestamp: 1763104757 Timestamp [UCT]: 2025-11-14 07:19:17 Age [y:d:h:m:s]: 00:006:17:18:20
Block: 1411797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4790 RingCT/type: yes/0
Extra: 0134c6fafde80c8b9174bd50bef2e836c3020dde138a6d3b0c88e2b6049e721e01021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02aee90a233a92e2bb9e865e33623e299877b0cf7e3e97865a1570a780730c2a 0.600000000000 1900260 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": 1411807, "vin": [ { "gen": { "height": 1411797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02aee90a233a92e2bb9e865e33623e299877b0cf7e3e97865a1570a780730c2a" } } ], "extra": [ 1, 52, 198, 250, 253, 232, 12, 139, 145, 116, 189, 80, 190, 242, 232, 54, 195, 2, 13, 222, 19, 138, 109, 59, 12, 136, 226, 182, 4, 158, 114, 30, 1, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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