Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a4d8cbfa4e4f93dd1c1d769f4b4d5cb181c5dd002a5fe80eb6541f3819f251d

Tx prefix hash: 5c6f104f3524af0ba120950a6f31194ae11b79b1069bd1f5755a215e839aee96
Tx public key: 93ba3f47e43a1a90e4c805cbaccbc14e42b7154269dfe5d03a6d6e2cfe35dc08
Timestamp: 1769794583 Timestamp [UTC]: 2026-01-30 17:36:23 Age [y:d:h:m:s]: 00:292:02:26:34
Block: 1467044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214312 RingCT/type: yes/0
Extra: 0193ba3f47e43a1a90e4c805cbaccbc14e42b7154269dfe5d03a6d6e2cfe35dc08021100000003215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 88259fd298023ebc518bf66ceee08d5c3805b270497965cd414036f4bdf3aa6e 0.000600000000 1956284 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": 1467054, "vin": [ { "gen": { "height": 1467044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88259fd298023ebc518bf66ceee08d5c3805b270497965cd414036f4bdf3aa6e" } } ], "extra": [ 1, 147, 186, 63, 71, 228, 58, 26, 144, 228, 200, 5, 203, 172, 203, 193, 78, 66, 183, 21, 66, 105, 223, 229, 208, 58, 109, 110, 44, 254, 53, 220, 8, 2, 17, 0, 0, 0, 3, 33, 91, 191, 137, 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: