Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d51b7e4d24f342ad0e8f0137c59cf250e2af0ee5ef40118ddd8b1fd2b7db30c

Tx prefix hash: 6b221224731d48703eb5c560f8b2e3681176fb507919ed8d943c25c3f2a428a3
Tx public key: 5add95ca8ea8d112466f11ee16d58b032216f81384d8b98855cd9845d04ea28c
Timestamp: 1750360332 Timestamp [UTC]: 2025-06-19 19:12:12 Age [y:d:h:m:s]: 01:151:05:41:10
Block: 1308562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372203 RingCT/type: yes/0
Extra: 015add95ca8ea8d112466f11ee16d58b032216f81384d8b98855cd9845d04ea28c021100000001d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c151a08314c1607b5f4c03e17e4e9c194141da2ce2aeaf11610a4e9263e11f0a 0.000600000000 1796175 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": 1308572, "vin": [ { "gen": { "height": 1308562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c151a08314c1607b5f4c03e17e4e9c194141da2ce2aeaf11610a4e9263e11f0a" } } ], "extra": [ 1, 90, 221, 149, 202, 142, 168, 209, 18, 70, 111, 17, 238, 22, 213, 139, 3, 34, 22, 248, 19, 132, 216, 185, 136, 85, 205, 152, 69, 208, 78, 162, 140, 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: