Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bfeef70de4aeebc97f20cf99399347383d1f89bafba4177be5784dd3885fac2

Tx prefix hash: 46f15ed0f8373269b05c4398474c09aa7a3b418a26e14961ea65d184ccced061
Tx public key: a34bf6da796e1acb45fb4a6df54e40d98d96db5ae851bd6e15e3a477fedd6bed
Timestamp: 1771635585 Timestamp [UTC]: 2026-02-21 00:59:45 Age [y:d:h:m:s]: 00:270:19:30:13
Block: 1482291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199080 RingCT/type: yes/0
Extra: 01a34bf6da796e1acb45fb4a6df54e40d98d96db5ae851bd6e15e3a477fedd6bed021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cf73b8b816b2e3acb897fc41e021f0df0445f7d3144ab3e943e166744393c372 0.000600000000 1971683 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": 1482301, "vin": [ { "gen": { "height": 1482291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf73b8b816b2e3acb897fc41e021f0df0445f7d3144ab3e943e166744393c372" } } ], "extra": [ 1, 163, 75, 246, 218, 121, 110, 26, 203, 69, 251, 74, 109, 245, 78, 64, 217, 141, 150, 219, 90, 232, 81, 189, 110, 21, 227, 164, 119, 254, 221, 107, 237, 2, 17, 0, 0, 0, 1, 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: