Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b29ddea4f47f715a15504340658d570c9d9ccbf67f5259d36713f60b2946ee1

Tx prefix hash: 9b97c62bebffaf4ad742803d6a1c521fb3d8b0a853e55ba3163962d9d99c9d4a
Tx public key: 3f785b722bb8f1c496f3bc3842e22cf66b982ff6fbc3304cb1a62a5b9a6fc432
Timestamp: 1769447934 Timestamp [UTC]: 2026-01-26 17:18:54 Age [y:d:h:m:s]: 00:293:07:41:08
Block: 1464176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215107 RingCT/type: yes/0
Extra: 013f785b722bb8f1c496f3bc3842e22cf66b982ff6fbc3304cb1a62a5b9a6fc432021100000002215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 558aaf3989c302e7b5e883d159d539b27f3a6da0580e6c41fb03897fad1d5ad9 0.000600000000 1953400 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": 1464186, "vin": [ { "gen": { "height": 1464176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "558aaf3989c302e7b5e883d159d539b27f3a6da0580e6c41fb03897fad1d5ad9" } } ], "extra": [ 1, 63, 120, 91, 114, 43, 184, 241, 196, 150, 243, 188, 56, 66, 226, 44, 246, 107, 152, 47, 246, 251, 195, 48, 76, 177, 166, 42, 91, 154, 111, 196, 50, 2, 17, 0, 0, 0, 2, 33, 91, 191, 137, 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: