Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4db909960e8a6d11142da272dc760307e5e8a756e5b15578ce764c0a59da068f

Tx prefix hash: 9431d47982d8f6a8a8becb50f227535d375dd4a5979a4ffcffe6501ed058111a
Tx public key: ad49b8f21b045cf4293be6e57673f8fddfe86742cc73f16bb37c9de3ef57f7c9
Timestamp: 1770550272 Timestamp [UTC]: 2026-02-08 11:31:12 Age [y:d:h:m:s]: 00:090:14:04:23
Block: 1473325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57432 RingCT/type: yes/0
Extra: 01ad49b8f21b045cf4293be6e57673f8fddfe86742cc73f16bb37c9de3ef57f7c9021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 89e0fbb840f70f5a129fed10120f772f5d677a80c7727c40a7153472ebfb6b41 0.000600000000 1962607 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": 1473335, "vin": [ { "gen": { "height": 1473325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89e0fbb840f70f5a129fed10120f772f5d677a80c7727c40a7153472ebfb6b41" } } ], "extra": [ 1, 173, 73, 184, 242, 27, 4, 92, 244, 41, 59, 230, 229, 118, 115, 248, 253, 223, 232, 103, 66, 204, 115, 241, 107, 179, 124, 157, 227, 239, 87, 247, 201, 2, 17, 0, 0, 0, 3, 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: