Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 477966128a18e7e6efd2cd3fe215d100ea4946bea8633d71ae7f62c6f01bf178

Tx prefix hash: d8c5d620684e9abef9e842856cc0b9f680af395e010cc68d7b4d2c1f8be9a963
Tx public key: b5d785273c072cf1c107970faeb58494e7218c65a86de89f93e1145f04c22576
Timestamp: 1771646617 Timestamp [UTC]: 2026-02-21 04:03:37 Age [y:d:h:m:s]: 00:270:17:32:23
Block: 1482381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199022 RingCT/type: yes/0
Extra: 01b5d785273c072cf1c107970faeb58494e7218c65a86de89f93e1145f04c2257602110000000be4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9342a87092735f982b92f1c5ad987b3567b9947cd8aa9622ebb6f94a93366362 0.000600000000 1971773 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": 1482391, "vin": [ { "gen": { "height": 1482381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9342a87092735f982b92f1c5ad987b3567b9947cd8aa9622ebb6f94a93366362" } } ], "extra": [ 1, 181, 215, 133, 39, 60, 7, 44, 241, 193, 7, 151, 15, 174, 181, 132, 148, 231, 33, 140, 101, 168, 109, 232, 159, 147, 225, 20, 95, 4, 194, 37, 118, 2, 17, 0, 0, 0, 11, 228, 245, 25, 63, 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: