Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61651da9d8a93e078bf8446d5d0f071fb97c2c68674fe365914b26cb93a4da09

Tx prefix hash: 6b3dad758f4c62559403919eeb265b14395ead0beab971c039868593a32563a7
Tx public key: a473e473719603f22150c5bd3547cf44043014bdf66121c98bd12c36455c90aa
Timestamp: 1770249137 Timestamp [UTC]: 2026-02-04 23:52:17 Age [y:d:h:m:s]: 00:104:10:52:31
Block: 1470841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 68085 RingCT/type: yes/0
Extra: 01a473e473719603f22150c5bd3547cf44043014bdf66121c98bd12c36455c90aa020879078cb62cd7b3f9

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b532213b8a7f93b3893ce1fd1f3284d72f44ee74bc4250bb59ae6f5fc11244e5 0.000600000000 1960111 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": 1470851, "vin": [ { "gen": { "height": 1470841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b532213b8a7f93b3893ce1fd1f3284d72f44ee74bc4250bb59ae6f5fc11244e5" } } ], "extra": [ 1, 164, 115, 228, 115, 113, 150, 3, 242, 33, 80, 197, 189, 53, 71, 207, 68, 4, 48, 20, 189, 246, 97, 33, 201, 139, 209, 44, 54, 69, 92, 144, 170, 2, 8, 121, 7, 140, 182, 44, 215, 179, 249 ], "rct_signatures": { "type": 0 } }


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