Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0580d185af98cfc8425fee0ebe770d71d70d469e7365dd5f722ea5afbb529d67

Tx prefix hash: 04824c1f965d61fb6355d391f4ad04c77db2283bf516ffc41862a0aaf76e269d
Tx public key: 9647ffbe2fb8eba069ff16cd5eb5f5d4705c2d634fa4e55746241a71d7c32ee2
Timestamp: 1767890012 Timestamp [UTC]: 2026-01-08 16:33:32 Age [y:d:h:m:s]: 00:314:16:16:26
Block: 1451449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230320 RingCT/type: yes/0
Extra: 019647ffbe2fb8eba069ff16cd5eb5f5d4705c2d634fa4e55746241a71d7c32ee2021100000007215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a9fbf2422300357407f7a8afff59d9a4b7cabbb7a5e39ad616df47a0273ec977 0.000600000000 1940461 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": 1451459, "vin": [ { "gen": { "height": 1451449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9fbf2422300357407f7a8afff59d9a4b7cabbb7a5e39ad616df47a0273ec977" } } ], "extra": [ 1, 150, 71, 255, 190, 47, 184, 235, 160, 105, 255, 22, 205, 94, 181, 245, 212, 112, 92, 45, 99, 79, 164, 229, 87, 70, 36, 26, 113, 215, 195, 46, 226, 2, 17, 0, 0, 0, 7, 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: