Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8241a52e6181bdc03f5931b7e45bd51f01d58c89a1caef9880f426ba2ca2145

Tx prefix hash: 642235d087a17c2775a19b6647a830236d6e0c22ed5db60d281076245cd09c3c
Tx public key: bf7ae46e39cd62ef9567ccc6c60b0978816e45c38c01b610540b9b48539d91a4
Timestamp: 1750583454 Timestamp [UTC]: 2025-06-22 09:10:54 Age [y:d:h:m:s]: 01:152:21:26:14
Block: 1310354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373140 RingCT/type: yes/0
Extra: 01bf7ae46e39cd62ef9567ccc6c60b0978816e45c38c01b610540b9b48539d91a4021100000001d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5c78944dc416cd09ccf3764aff8bfda4c12c2f9678446937e6833cf4581bdcde 0.000600000000 1797973 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": 1310364, "vin": [ { "gen": { "height": 1310354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c78944dc416cd09ccf3764aff8bfda4c12c2f9678446937e6833cf4581bdcde" } } ], "extra": [ 1, 191, 122, 228, 110, 57, 205, 98, 239, 149, 103, 204, 198, 198, 11, 9, 120, 129, 110, 69, 195, 140, 1, 182, 16, 84, 11, 155, 72, 83, 157, 145, 164, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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: