Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfcb0216644dd76efa9edca52bfe1733aea708e5e403ba2a5dfab49a0aef55a5

Tx prefix hash: 1edcd766c3b41e4e6e3e3db3a781827b02678eb0a572ba1a7a163246bbd9771d
Tx public key: b96444a630886259a8afaf361476dbba52c1eebffc9713935f3775bf34cc7353
Timestamp: 1747964055 Timestamp [UTC]: 2025-05-23 01:34:15 Age [y:d:h:m:s]: 01:182:03:19:07
Block: 1288857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394321 RingCT/type: yes/0
Extra: 01b96444a630886259a8afaf361476dbba52c1eebffc9713935f3775bf34cc73530211000000041f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd526e3844a7cc1960aa4ecdf6d0672041defba55c9d76dbc0be2dc1422ef6ea 0.000600000000 1776324 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": 1288867, "vin": [ { "gen": { "height": 1288857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd526e3844a7cc1960aa4ecdf6d0672041defba55c9d76dbc0be2dc1422ef6ea" } } ], "extra": [ 1, 185, 100, 68, 166, 48, 136, 98, 89, 168, 175, 175, 54, 20, 118, 219, 186, 82, 193, 238, 191, 252, 151, 19, 147, 95, 55, 117, 191, 52, 204, 115, 83, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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: