Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4df620e9818ae928dc43f166d411dd6fb8a0d08c6ba75c45e61906e5f915ead3

Tx prefix hash: 47a3319a80f32ea933d24e21742fe465d129515cd5359b680a746e2ba0134656
Tx public key: 1ba802b21c3a90280005592fe0ddc7d40ce54603b5f5527d7f8311e23cccde8c
Timestamp: 1743977707 Timestamp [UTC]: 2025-04-06 22:15:07 Age [y:d:h:m:s]: 01:041:22:54:51
Block: 1255831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281120 RingCT/type: yes/0
Extra: 011ba802b21c3a90280005592fe0ddc7d40ce54603b5f5527d7f8311e23cccde8c02110000000adbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 294bfc18c5bd03d84402d8ea30304b8fbc53c01be77380ae74b0652928bf1660 0.000600000000 1742938 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": 1255841, "vin": [ { "gen": { "height": 1255831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "294bfc18c5bd03d84402d8ea30304b8fbc53c01be77380ae74b0652928bf1660" } } ], "extra": [ 1, 27, 168, 2, 178, 28, 58, 144, 40, 0, 5, 89, 47, 224, 221, 199, 212, 12, 229, 70, 3, 181, 245, 82, 125, 127, 131, 17, 226, 60, 204, 222, 140, 2, 17, 0, 0, 0, 10, 219, 181, 113, 193, 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: