Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b1bb8fd84b90a40bd5be5104bfe45ebbf66520006069dcfaf9c4f724f5d93e2

Tx prefix hash: f0f2ee54d921b36459d4a28b74002fe384e8f3c78a124c0003f3dbb4285ea2d5
Tx public key: 3fdf35f24240fadafb284e01ea25bdf2043b4171bdb6a33e2334414c3648e384
Timestamp: 1784372715 Timestamp [UTC]: 2026-07-18 11:05:15 Age [y:d:h:m:s]: 00:124:19:48:58
Block: 1584442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 98044 RingCT/type: yes/0
Extra: 013fdf35f24240fadafb284e01ea25bdf2043b4171bdb6a33e2334414c3648e38402086246df531bec069c

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 675b9a424255f4d6fe803fdcda33f1c093ec56ba668e25f683be5f851832343c 0.000600000000 2074436 of 15 <d6>

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": 1584452, "vin": [ { "gen": { "height": 1584442 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "675b9a424255f4d6fe803fdcda33f1c093ec56ba668e25f683be5f851832343c", "view_tag": "d6" } } } ], "extra": [ 1, 63, 223, 53, 242, 66, 64, 250, 218, 251, 40, 78, 1, 234, 37, 189, 242, 4, 59, 65, 113, 189, 182, 163, 62, 35, 52, 65, 76, 54, 72, 227, 132, 2, 8, 98, 70, 223, 83, 27, 236, 6, 156 ], "rct_signatures": { "type": 0 } }


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