Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 514030f2bc3b77663c35d49b5ff8fb8d3e43b3bda053b47436c4372fb90aa41f

Tx prefix hash: f0c7429d0e4f48ad9d44e2535a40dbb7704d0c1b6c61aacfb309c1f594ca0f4c
Tx public key: d5e647a0661e233f0b71fa34731b2d11d4e54e4f9cfecfd7ad848e068f25f9e9
Timestamp: 1785517769 Timestamp [UTC]: 2026-07-31 17:09:29 Age [y:d:h:m:s]: 00:108:12:26:28
Block: 1602955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 77215 RingCT/type: yes/0
Extra: 01d5e647a0661e233f0b71fa34731b2d11d4e54e4f9cfecfd7ad848e068f25f9e9

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bdfe0d8f09d2eee68cd8045c2a8ebf7abb3dc67bb9e0440265ef524a50128326 0.000600000000 2092973 of 15 <42>

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": 1602965, "vin": [ { "gen": { "height": 1602955 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "bdfe0d8f09d2eee68cd8045c2a8ebf7abb3dc67bb9e0440265ef524a50128326", "view_tag": "42" } } } ], "extra": [ 1, 213, 230, 71, 160, 102, 30, 35, 63, 11, 113, 250, 52, 115, 27, 45, 17, 212, 229, 78, 79, 156, 254, 207, 215, 173, 132, 142, 6, 143, 37, 249, 233 ], "rct_signatures": { "type": 0 } }


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