Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc022575c54ed5e3ce2edf749196e294fafe2924de50e0ae2360505e6c752939

Tx prefix hash: 5c6e6710eae55b8ca7421fadfc780da1254695a32cd22d391cd85bbb7817ea31
Tx public key: 4cc8839a433cb08f422da21a4d9e3ddcf9c3c113d17ef5d3bf47778b8c67fad4
Timestamp: 1645591958 Timestamp [UTC]: 2022-02-23 04:52:38 Age [y:d:h:m:s]: 04:271:02:56:23
Block: 444536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1237984 RingCT/type: yes/0
Extra: 014cc8839a433cb08f422da21a4d9e3ddcf9c3c113d17ef5d3bf47778b8c67fad4021100000003bf7ee4e7000000000000000000

1 output(s) for total of 0.020657034893 xmr

stealth address amount amount idx tag
00: 48f31e1e3c8e6e4c5c2667331baee492d637fac506576cba56747f031568f0e4 0.020657034893 857853 of 0 -

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": 444546, "vin": [ { "gen": { "height": 444536 } } ], "vout": [ { "amount": 20657034893, "target": { "key": "48f31e1e3c8e6e4c5c2667331baee492d637fac506576cba56747f031568f0e4" } } ], "extra": [ 1, 76, 200, 131, 154, 67, 60, 176, 143, 66, 45, 162, 26, 77, 158, 61, 220, 249, 195, 193, 19, 209, 126, 245, 211, 191, 71, 119, 139, 140, 103, 250, 212, 2, 17, 0, 0, 0, 3, 191, 126, 228, 231, 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: