Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac8e6708e106a7384ec0ec7d8dfdf72015b7bd9c9acd9422b16318cf6618cd34

Tx prefix hash: b3b443173fc22b3c964b17148e4246a9e406de86c6bca92c6643f257cb40e99f
Tx public key: 78afd71215776f4269dd46bb09f803dcc5bd73cc07be7b5373dcc49f4ce0912d
Timestamp: 1771028161 Timestamp [UTC]: 2026-02-14 00:16:01 Age [y:d:h:m:s]: 00:275:07:10:55
Block: 1477247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202246 RingCT/type: yes/0
Extra: 0178afd71215776f4269dd46bb09f803dcc5bd73cc07be7b5373dcc49f4ce0912d021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aa144fa0a0cd9e44ead8161c193c75867e2671f302af4d6aa0d19e9592b64572 0.000600000000 1966561 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": 1477257, "vin": [ { "gen": { "height": 1477247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa144fa0a0cd9e44ead8161c193c75867e2671f302af4d6aa0d19e9592b64572" } } ], "extra": [ 1, 120, 175, 215, 18, 21, 119, 111, 66, 105, 221, 70, 187, 9, 248, 3, 220, 197, 189, 115, 204, 7, 190, 123, 83, 115, 220, 196, 159, 76, 224, 145, 45, 2, 17, 0, 0, 0, 3, 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: