Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28ca9b95624d628468c4cd6cd4ebc4fdb63569efe6ca5d73c5cc444a5a35f162

Tx prefix hash: cc5af1447daad0949fd08c6a74d357587c4bc606c59ed9ced508271e30d592c5
Tx public key: 80623b24bac1d0e160a85ecedc545a1386dffc2aebfcabef4666dcce97d78dd7
Timestamp: 1772144101 Timestamp [UTC]: 2026-02-26 22:15:01 Age [y:d:h:m:s]: 00:263:22:01:50
Block: 1486484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194128 RingCT/type: yes/0
Extra: 0180623b24bac1d0e160a85ecedc545a1386dffc2aebfcabef4666dcce97d78dd7021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3a928c4868f1446e63995cc4f54edc3afa4b88ab6e58713430fbf04a303b9366 0.000600000000 1975940 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": 1486494, "vin": [ { "gen": { "height": 1486484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a928c4868f1446e63995cc4f54edc3afa4b88ab6e58713430fbf04a303b9366" } } ], "extra": [ 1, 128, 98, 59, 36, 186, 193, 208, 225, 96, 168, 94, 206, 220, 84, 90, 19, 134, 223, 252, 42, 235, 252, 171, 239, 70, 102, 220, 206, 151, 215, 141, 215, 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: