Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e92c810591e5ccd4a0bc472f9c2e158dd0e5defb4763f79e73a72526601955ca

Tx prefix hash: c6569275f4f5e650b1a7a027b03210e5f9a7618323ab0a9476bc8e2a4a00ae5a
Tx public key: 2b4910be0ef274e8cb17d9b51161a7636f6baabd63ddb502ee708680e4ae4827
Timestamp: 1744856804 Timestamp [UCT]: 2025-04-17 02:26:44 Age [y:d:h:m:s]: 00:218:21:59:57
Block: 1263121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154186 RingCT/type: yes/0
Extra: 012b4910be0ef274e8cb17d9b51161a7636f6baabd63ddb502ee708680e4ae48270211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b9addb005ab66d118011ced365c23527836b41418f2c489363b37a1b919d67e 0.600000000000 1750304 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": 1263131, "vin": [ { "gen": { "height": 1263121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b9addb005ab66d118011ced365c23527836b41418f2c489363b37a1b919d67e" } } ], "extra": [ 1, 43, 73, 16, 190, 14, 242, 116, 232, 203, 23, 217, 181, 17, 97, 167, 99, 111, 107, 170, 189, 99, 221, 181, 2, 238, 112, 134, 128, 228, 174, 72, 39, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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