Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef4d5023726e350dd7dcca9776729e3b985c49bc0e0f091a39708410ec954bdf

Tx prefix hash: df3b721513c52da329cdadfcce770ddd65bfeb931b679d89d478c6e34d5c7a55
Tx public key: 0dd0a81a577b0473affd38dc364dec0327293b0933b36304c4d000249b88ed5c
Timestamp: 1770768810 Timestamp [UTC]: 2026-02-11 00:13:30 Age [y:d:h:m:s]: 00:003:06:49:02
Block: 1475132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 2322 RingCT/type: yes/0
Extra: 010dd0a81a577b0473affd38dc364dec0327293b0933b36304c4d000249b88ed5c02087e0365602bd68945

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f6e9756c920c94a64e9ac4def8935295a387ed8f4a36bc077a47903c83c58e44 0.000600000000 1964430 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 dinastycoin-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": 1475142, "vin": [ { "gen": { "height": 1475132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6e9756c920c94a64e9ac4def8935295a387ed8f4a36bc077a47903c83c58e44" } } ], "extra": [ 1, 13, 208, 168, 26, 87, 123, 4, 115, 175, 253, 56, 220, 54, 77, 236, 3, 39, 41, 59, 9, 51, 179, 99, 4, 196, 208, 0, 36, 155, 136, 237, 92, 2, 8, 126, 3, 101, 96, 43, 214, 137, 69 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369