Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2524b0c2f75a9ce1bb5569d06878a0065dbabffad112932a7bc4d5b0a02ff682

Tx prefix hash: e3b47dcf3aa40c0cd52acf788f5395514f949cd1bbb04f78434917f0396f56c8
Tx public key: 2695a0b540b80c024f4b8f2e1319d9929b7bbbc13ab93d6c2db21e072a0c75e5
Timestamp: 1770632143 Timestamp [UTC]: 2026-02-09 10:15:43 Age [y:d:h:m:s]: 00:004:12:38:33
Block: 1474008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 3202 RingCT/type: yes/0
Extra: 012695a0b540b80c024f4b8f2e1319d9929b7bbbc13ab93d6c2db21e072a0c75e502088fbad2eb0ae6e744

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bcb8bf4b6963f28845cf8527177ea76396c91fb130dfe87d9b5d2bb4d4e169b4 0.000600000000 1963302 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": 1474018, "vin": [ { "gen": { "height": 1474008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcb8bf4b6963f28845cf8527177ea76396c91fb130dfe87d9b5d2bb4d4e169b4" } } ], "extra": [ 1, 38, 149, 160, 181, 64, 184, 12, 2, 79, 75, 143, 46, 19, 25, 217, 146, 155, 123, 187, 193, 58, 185, 61, 108, 45, 178, 30, 7, 42, 12, 117, 229, 2, 8, 143, 186, 210, 235, 10, 230, 231, 68 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369