Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71c821d4993c42c2d056a3c7db4ee852850a3aa7b756bc4da20276cbe21a695f

Tx prefix hash: 8f2dfba57d639b0abd84bb5e77e434eff36ceb5136bee4e9719a366b94cea965
Tx public key: e54a350f425d610908354e4cc9c429ec41b1936ff8aaac9408fdb61a3771f6e1
Timestamp: 1744079979 Timestamp [UTC]: 2025-04-08 02:39:39 Age [y:d:h:m:s]: 01:221:22:45:35
Block: 1256679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422623 RingCT/type: yes/0
Extra: 01e54a350f425d610908354e4cc9c429ec41b1936ff8aaac9408fdb61a3771f6e10211000000046c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 465810b9368a6b76d3440f3b92cbc9b859dd0afe689ce8174adb6f8811be3924 0.000600000000 1743796 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": 1256689, "vin": [ { "gen": { "height": 1256679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "465810b9368a6b76d3440f3b92cbc9b859dd0afe689ce8174adb6f8811be3924" } } ], "extra": [ 1, 229, 74, 53, 15, 66, 93, 97, 9, 8, 53, 78, 76, 201, 196, 41, 236, 65, 177, 147, 111, 248, 170, 172, 148, 8, 253, 182, 26, 55, 113, 246, 225, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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: