Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2bd67d050dc634954b58a182578adeaf85dc7e4b15e5cef1997b5d958bde53c

Tx prefix hash: 611c4e4c8b7028c472bf2d9ff90b3f0eceeb3e371ee35832e51b0ea48d59d8ef
Tx public key: 7c9140f6b47a090634b844ca8b0e1451dca522a8c3b394e958aedfd54cbdef9e
Timestamp: 1716466651 Timestamp [UTC]: 2024-05-23 12:17:31 Age [y:d:h:m:s]: 02:181:03:02:11
Block: 1028270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 654515 RingCT/type: yes/0
Extra: 017c9140f6b47a090634b844ca8b0e1451dca522a8c3b394e958aedfd54cbdef9e0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 389c33f61cbc1bcc9d16de93b1a7e52008f97947f01e9884605f3c622935c78f 0.000600000000 1496245 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": 1028280, "vin": [ { "gen": { "height": 1028270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "389c33f61cbc1bcc9d16de93b1a7e52008f97947f01e9884605f3c622935c78f" } } ], "extra": [ 1, 124, 145, 64, 246, 180, 122, 9, 6, 52, 184, 68, 202, 139, 14, 20, 81, 220, 165, 34, 168, 195, 179, 148, 233, 88, 174, 223, 213, 76, 189, 239, 158, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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: