Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffb89859fced4890e173c960ca79dad1dfd5e30dfa50ae10be4305db388be4b7

Tx prefix hash: 296b4f8921745d2e2ceeffeb94a561cf06a726d51e2623360fb38f9fa40e069c
Tx public key: f1d40092e8152baeb2ca345eb39184a2bfae0aa562f7dcf63eefc17e87fcebb1
Timestamp: 1771331835 Timestamp [UTC]: 2026-02-17 12:37:15 Age [y:d:h:m:s]: 00:273:03:07:43
Block: 1479764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200707 RingCT/type: yes/0
Extra: 01f1d40092e8152baeb2ca345eb39184a2bfae0aa562f7dcf63eefc17e87fcebb1021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aae5291792d23805848c89e80a863acd06f0ae928e71c9a4ef241cbe9033b9cb 0.000600000000 1969120 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": 1479774, "vin": [ { "gen": { "height": 1479764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aae5291792d23805848c89e80a863acd06f0ae928e71c9a4ef241cbe9033b9cb" } } ], "extra": [ 1, 241, 212, 0, 146, 232, 21, 43, 174, 178, 202, 52, 94, 179, 145, 132, 162, 191, 174, 10, 165, 98, 247, 220, 246, 62, 239, 193, 126, 135, 252, 235, 177, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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